On Mon, 22 Oct 2007 12:41:07 -0400 Ryan Pugatch <[EMAIL PROTECTED]> wrote:
> > > Harald Braumann wrote: > > On Mon, 22 Oct 2007 10:54:21 -0400 > > Ryan Pugatch <[EMAIL PROTECTED]> wrote: > > > > > >> (gdb) run > >> Starting program: /usr/local/bin/sm > >> [Thread debugging using libthread_db enabled] > >> [New Thread -1208580416 (LWP 20792)] > >> Error while reading shared library symbols: > >> Cannot find new threads: generic error > >> > >> Program received signal SIGSEGV, Segmentation fault. > >> [Switching to Thread -1208580416 (LWP 20792)] > >> 0x00000030 in ?? () > >> (gdb) > >> > >> Doesn't seem to have a lot of info, though there's a chance I'm > >> not using gdb properly. > >> > > You should recompile sm with debugging enabled (call ./configure > > --enable-developer). Maybe you should also add `-O0' to CFLAGS to > > prevent gcc from optimizing away variables. > > > > Then gdb should show the source line at the fault. Also you can then > > print a backtrace and examine variable values at that point. > > > > Regards, > > harry > I just gave this a shot and GDB isn't giving me any additional info, > nor did a backtrace. At a loss as to what to do now. Hm, that's strange. It should print the source line automatically. And you get a backtrace by typing ``bt''. So either the source wasn't recompiled with debugging symbols (you did do a ``make clean'' before ``make'', right?) or your gdb is fucked. The errors at the beginning of the output are a bit disturbing, but I don't know if that's the problem. Regards, harry _______________________________________________ Jabberd2 mailing list [email protected] http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
