If the program is dynamically linked, you can try "ldd qmail-smtp" to see what libraries it links to.
The debugging result looks weird to me. I don't know what's going on but possibly the process forked another process ... Let's sit down and wait for experienced gdb users to appear. :-) Best Regards, Puqing On Jan 24, 2008 10:17 AM, Eugene Teo <[EMAIL PROTECTED]> wrote: > Hi, > > P.V.Anthony wrote: > > Trying to debug qmail-smtp as it segfault after a patch. > > > > Compiled qmail with flags -ggdb and removed the -s flag. > [...] > > Program received signal SIGSEGV, Segmentation fault. > > 0x00005555555669ea in ?? () > > (gdb) backtrace > > #0 0x00005555555669ea in ?? () > > #1 0x0000000000000000 in ?? () > > (gdb) frame 0 > > #0 0x00005555555669ea in ?? () > > (gdb) frame 1 > > #1 0x0000000000000000 in ?? () > > (gdb) > > Compiling qmail with -g is insufficient. You also need the debuginfo > of the libraries that are linked to qmail. If you were using a distribution > like Fedora or Red Hat Enterprise Linux, all you have to do is to find > out which library is linked, download the relevant debuginfo rpms, install > them, and rerun gdb. This should give you more meaningful output. > > Thanks, > Eugene > > > _______________________________________________ > Slugnet mailing list > [email protected] > http://www.lugs.org.sg/mailman/listinfo/slugnet > -- Best Regards, Puqing Chen [EMAIL PROTECTED] _______________________________________________ Slugnet mailing list [email protected] http://www.lugs.org.sg/mailman/listinfo/slugnet
