Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems with writing on closed pipe exceptions using os. #20

Open
GoogleCodeExporter opened this issue Mar 14, 2015 · 1 comment
Open

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. download the pgw dictionary
2. run   cat /lib/dict/pgwindex  | os awk '{print $1}' | sed 100q 

What is the expected output? What do you see instead?

I'd expect the command to terminate. Instead it stays in permanently stuck 
status. I think this is a 
problem with  the difference between Sys and things run in limbo modules. When 
OS handles an 
exception it doesn't propagate back to the shell. 


Original issue reported on code.google.com by [email protected] on 19 Jan 2009 at 11:59

@GoogleCodeExporter
Copy link
Author

I'm seeing the problem with:

  cat /lib/dict/pgwindex  | getlines {
    (word nil)=`{echo $line}
    echo $word
}| sed 100q 

as well. This indicates that's its not quite the problem I expected. 

Original comment by [email protected] on 20 Jan 2009 at 12:07

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant