{#} Replies are directed back to [EMAIL PROTECTED]
{#} To reply to the author, write to Theo Schlossnagle <[EMAIL PROTECTED]>
On Sunday, January 20, 2002, at 07:48 PM, Charlie Orme wrote:
> I've been having a vexing problem with Fire for quite some time now.
> Whenever I try to connect to AIM in it, it unexpectedly quits (and if I
> 'm running it in debug, I get "Program received signal: SIGPIPE"). The
> unusual thing is that this behavior is totally random. Sometimes, it
> will do this for hours on end, and nothing (even clean CVS checkouts)
> can fix it. Other times, it doesn't do it. Always, I get a delay of
> about 25 seconds when connecting. My buddy list has 174 people on it;
> could this be causing the problem?
As a note on debugging. Using gdb (even from Project Builder), just
type:
handle SIGPIPE nostop
handle SIGPIPE pass
after you get the first signal and it _should_ ignore them from that
point on. By default, gdb doesn't interfere with the PIPE signal, but
Project Builder may take liberties with the default settings of its
wrapped gdb?
--
Theo Schlossnagle
1024D/82844984/95FD 30F1 489E 4613 F22E 491A 7E88 364C 8284 4984
2047R/33131B65/71 F7 95 64 49 76 5D BA 3D 90 B9 9F BE 27 24 E7
{#} ----------------------------------------------------+[ fire ]+---
