Date: Fri, 11 Jan 2002 12:35:24 -0800 From: Mike Makonnen <mike_makonnen@yahoo.com> To: Dave Runkle <dave@runkle.com> Cc: freebsd-questions@freebsd.org Subject: Re: Sylpheed dumps core when starting Message-ID: <200201112035.g0BKZOx91746@blackbox.pacbell.net> In-Reply-To: <20020111083808.L62722-100000@trittico.fiddi.com> References: <20020111182500.60804342.sdg@rila.bg> <20020111083808.L62722-100000@trittico.fiddi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 11 Jan 2002 08:46:12 -0800 (PST) Dave Runkle <dave@runkle.com> wrote: > Can someone give me an idea or tip about how to find the cause of > this segfault? How can I diagnose it? I've ulimit-ed cores, I could > allow them again but wouldn't know what to do with it anyway. > (I'm assuming it wasn't compiled with debugging symbols enabled) 1. Using the same exact sources from which you compiled the segfaulted program, build a new executable with debugging enabled: # cd /usr/ports/...../sylpheed # env CFLAGS=-g make 2. start gdb and specify the core file and the executable you are using # gdb /program /path/to/corefile 3. Once in gdb use the command 'where' or 'bt' to figure out where you're segfaulting. You can then examine variables, data structures, etc, to get an idea of where and why it's segfaulting. Cheers, mike makonnen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200201112035.g0BKZOx91746>