On Tue, Apr 18, 2006 at 10:22:50PM -0400, Luke Reeves wrote: > Package: firefox > Version: 1.5.dfsg+1.5.0.1-4 > Followup-For: Bug #306537 > > I managed to capture a stack trace. Here it is for > what it's worth: > > Program received signal SIGPIPE, Broken pipe. Sigpipe means writing to a pipe without a reader, and the default action *is* to be killed. I don't know why send() would be used for anything but a socket, since write() does the same thing, but well.
pipe(7): If all file descriptors referring to the read end of a pipe have been closed, then a write(2) will cause a SIGPIPE signal to be generated for the calling process Anyway, the stack trace looks corrupted. Can you reproduce this bug as a new user with firefox -safe-mode? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]