SYSV vs BSD signal blues :-(
Hello, We've seen some signal related troubles when building the RTS lately. This is about what's happening: * GPC's RTS installs a signal handler to give pretty error messages when a signal is caught. This is ONLY implemented for BSD like systems, probably because Juki didn't have access to a SYSV style box. * SYSV and BSD differ in the number of signals and their meaning. * Some BSD boxes don't implement all signals > 16. (SIGXCPU etc.) * Some SYSV boxes implement (a range of) BSD-only signals, making it hard to dectect a true BSD box. I'm getting tired of writing ever more clever system identification routines that break on the next system I encounter. I think I'll just rewrite the signal related stuff in rts-rt0.c, implement some BSD/SYSV independant routines that ONLY mask signals that are actually present on the target system. How 'bout it? JanJaap --- The latest & greatest in software, hardware and manswear. Bono Vox (U2)
I think I'll just rewrite the signal related stuff in rts-rt0.c, implement some BSD/SYSV independant routines that ONLY mask signals that are actually present on the target system.
I have personally found this feature annoying. I DO want a core dump in the case of a SIGSEGV so I can see where it occured with a debugger. Should the default be not to have it and if you want it have a run time flag or a configure flag that enables by default? -- Phil Nelson NetBSD: http://www.netbsd.org e-mail: phil@cs.wwu.edu LPF: http://www.lpf.org http://www.cs.wwu.edu/~phil !gifs: http://www.lpf.org/Patent/Gif/Gif.html
participants (2)
-
J.J. van der Heijden -
Phil Nelson