hi there! i'm referring to gdb 5.0, glibc 2.2.3 on linux 2.4.5. 1) when a program catches a signal, and invokes gdb attaching it to itself and letting gdb create a backtrace, the topmost stack frame below the signal handler is invisible, i.e., the bt shows the function, which called the faulting function and then sigaction() right above it. i'm not exactly sure, if this is gdb's fault. 2) gdb does not remove breakpoint hooks after a fork. therefore, a dlopen() in a fork()ed process will crash with a sigtrap. greetings -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! -- Nothing is fool-proof to a sufficiently talented fool. _______________________________________________ Bug-gdb mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-gdb
