11 Sep
2006
11 Sep
'06
3:27 a.m.
On Sun, 2006-09-10 at 20:57 -0500, Monty J. Harder wrote:
I must be thick. Can you connect the dots between the two signals?
There's nothing between them. If they absolutely _must_ use SIGHUP because, presumably, some third party program is sending it to their debugging target, then they can put a interceptor process's PID in place of the PID file of the debugging target that is being sought out. This interceptor would catch the HUP and emit a SEGV to the real PID. The perl/ruby and even C <signal.h> code for this is less than 10 lines.
If there is no third party program emitting SIGHUP, then it doesn't matter what signal is received and backtraced by gdb. SIGSEGV just happens to be the easiest one to do that with ...