search

shhyou / ypsilon-fork

Automatically exported from code.google.com/p/ypsilon
Other
0 stars 0 forks source link

flush-output-port dies badly #52

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. (load "gtk-server-demo.ss") ;; requires gtk-server
2. (gtk-init)
3. (display "gtk_init NULL NULL" gtk-stdin)
4. (newline gtk-stdin)
5. (flush-output-port gtk-stdin) ;; Crashes Here

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

Expected to be able to continue execution; process died instead.

What version of the product are you using? On what operating system?

Ypsilon 0.9.6-trunk/r252
Linux sealed 2.6.24-21-generic #1 SMP Mon Aug 25 17:32:09 UTC 2008 i686 
GNU/Linux
gcc version 4.2.4 (Ubuntu 4.2.4-1ubuntu3)

Please provide any additional information below.

[Uncommented (run-test) works under plt-r6rs and larceny].

Original issue reported on code.google.com by Ken.Dic...@whidbey.com on 16 Oct 2008 at 4:36

Attachments:

GoogleCodeExporter commented 9 years ago 
Thank you for your bug report!

Original comment by y.fujita...@gmail.com on 16 Oct 2008 at 4:11

GoogleCodeExporter commented 9 years ago 
I found that procedure 'process' in Ypsilon can not handle parameter like 
"gtk-server
stdin nodetach" since it is very primitive wrapper for fork&execvp. I have 
added new
procedure 'process-shell-command' which can handle such parameter properly.

Please try attached 'process-compat.ypsilon.sls' and Ypsilon revision 256 in 
trunk.
They works fine on my system with gtk-server-demo.ss :)

Thank you!

Original comment by y.fujita...@gmail.com on 20 Oct 2008 at 4:40

Attachments:

GoogleCodeExporter commented 9 years ago 
Sorry, I forgot to mention about that there was another bug which cause
flush-output-port dead badly (no error message) on SIGPIPE. I have fixed that 
bug too
in revision 256.
--fujita

Original comment by y.fujita...@gmail.com on 20 Oct 2008 at 4:59

GoogleCodeExporter commented 9 years ago 
The code works very well now [v256].  A broken pipe is also reported properly.

Thanks much!
-KenD

Original comment by Ken.Dic...@whidbey.com on 20 Oct 2008 at 5:23

GoogleCodeExporter commented 9 years ago 
> The code works very well now [v256].  A broken pipe is also reported properly.
It's Great! Thank you!

Original comment by y.fujita...@gmail.com on 22 Oct 2008 at 12:39