From owner-freebsd-questions  Fri Jan 11 23: 2:16 2002
Delivered-To: freebsd-questions@freebsd.org
Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38])
	by hub.freebsd.org (Postfix) with ESMTP id 3B28A37B400
	for <freebsd-questions@FreeBSD.ORG>; Fri, 11 Jan 2002 23:02:08 -0800 (PST)
Received: from trittico.fiddi.com ([12.228.145.237]) by rwcrmhc51.attbi.com
          (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP
          id <20020112070207.XCJB10951.rwcrmhc51.attbi.com@trittico.fiddi.com>;
          Sat, 12 Jan 2002 07:02:07 +0000
Date: Fri, 11 Jan 2002 23:02:07 -0800 (PST)
From: Dave Runkle <dave@runkle.com>
X-X-Sender: dave@trittico.fiddi.com
To: Mike Makonnen <mike_makonnen@yahoo.com>
Cc: freebsd-questions@FreeBSD.ORG
Subject: Re: Sylpheed dumps core when starting
In-Reply-To: <200201112035.g0BKZOx91746@blackbox.pacbell.net>
Message-ID: <20020111230011.S92436-100000@trittico.fiddi.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-questions.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-questions>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-questions>
X-Loop: FreeBSD.ORG


Thank you, Mike, very much for this info. It's not nearly so
important for me to get Sylpheed up and running as it is for me to
learn this debugging process. Your clear description should make it
easy for me to do so.

Thanks very much!
Dave


On Fri, 11 Jan 2002, Mike Makonnen wrote:

> 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