Andrew Benton wrote: > Christian Biere wrote: > > Maybe try -g instead of -g3. You could also use --exec-on-crash or > > --pause-on-crash, then you don't need the core dump at all. > > Thanks, FWIW I got the -g3 from > http://gtk-gnutella.sourceforge.net/en/?page=bugreport_howto
Yes, -g3 is fine and preserves more information but it may still trigger a bug in gdb sometimes because it is not the default setting. > I don't know how to use --exec-on-crash or --pause-on-crash, are they > command line switches to pass to gtk-gnutella when I first start it? Yes, --exec-on-crash is explained here: http://sourceforge.net/mailarchive/message.php?msg_id=37504000 With --pause-on-crash the process is simply suspended when a crash occurs. You can then attach with gdb to the process and inspect it as usual: $ gdb /path/to/gtk-gnutella <pid> -- Christian ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Gtk-gnutella-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
