[EMAIL PROTECTED] wrote: > Hi > autogen-5.9.1 fails to build on Solaris (both Solaris 2.6 and Solaris 8) > because agen5/autogen always segfaults upon exit (from wherever the exit() > is called): The reason seems to be the "signalSetup( ignoreSignal, > abendSignal );" > which is called as the first thing in the main() program. The cause seems > not to be an erroneous signal handler routine (they seem to work and catch > the segfault, decorating it with a nice message), but the signalSetup() > itself, > which also leads to the fault when installing the default handlers. > > Workaround: comment out the above line, and the rest of the build > proceeds fine (who needs the nice messages anyway - the default OS handlers > also deliver a similar message to the same effect... ;-)
Hi Arto, So, I've been puzzling over this missive off and on trying to understand exactly what the issue is. signalSetup() boils down to a loop that sets up the desired handlers for the various signals. libc does _not_ produce a pretty informative message, which is why I wrote the cruft. The main reason a signal fires is because something took too long and you certainly want to know where in your template a failure occurred without having to analyze a core dump. So, anyway, it is needed. So, why does Solaris seg fault for you on this? (You should know that I use this on Solaris without such problems, so I'd like to understand...) - Bruce ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Autogen-users mailing list Autogen-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/autogen-users
