It's related because it explains the meaning of "segmentation fault". However, it also says that there are only two possibilities -- either there's a bug in the program or a hardware problem. If this error is consistent and repeatable at all hours of the day or night, it's not a hardware issue.
That leaves a software bug in gcc (because gcc is crashing, not spamdyke). Something about the structure, layout or size of spamdyke's code tickles this particular bug but without more information there's no way to understand exactly what's happening. Unfortunately, gcc is one of the most complex pieces of software ever created and debugging it is not a trivial task (I would rate it beyond "monumental" -- simply recompiling gcc is not for the timid). Because I can't fix gcc, all I can recommend is to contact the gcc authors or to change versions of gcc, if possible. Sorry. -- Sam Clippinger K. Shantanu wrote: > * Sam Clippinger <[EMAIL PROTECTED]> [081003 08:11]: > >> This looks like a problem with gcc. Version 3.4.6 is the most recent >> version before 4.x, so it might be worthwhile to submit a bug report to >> > [...] > > While reading FBSD FAQ, I chanced upon this. Does it seem related? > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#SIGNAL11 > > Thanks. > Shantanu > _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
