Re^2: unexpected quit - no error message

AH! Thanks - I am learning - did not know about

"This generates a SIGPIPE signal, whose default handler action is to abort the program (assuming you're on Unix)"

Yes, UNIX, is there any other OS? I will check for that out. Try to catch it.

two questions:
why $? = 0 = success on abort?
why an abort after> a successful write to the socket? - the device was updated AOK.

thanks other suggestions - I do have debug statements around the spot where it seems to quit - again they must have been executed but the output does not appear! I assume that if it is an abort, the output buffer is not written???

correction: using IO::Socket

Comment on Re^2: unexpected quit - no error message

Replies are listed 'Best First'.
Re^3: unexpected quit - no error message by almut (Canon) on Mar 02, 2009 at 19:18 UTC
two questions: why $? = 0 = success on abort? why an abort after a successful write to the socket? - the device was updated AOK. If we had something to look at, we'd need to guess less :) Could you show the significant parts of your code? Preferably also an strace of a run that did abort (the last 20, or so, lines should be sufficient, typically).	[reply]
Re^3: unexpected quit - no error message by CountZero (Bishop) on Mar 02, 2009 at 21:11 UTC
If you don't see the debug messages, you may be suffering from buffering. This may be especially the case when the program terminates unexpectedly and the script is not able to flush its buffers. CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James	[reply]