From owner-freebsd-questions  Fri Jan 11 12:35: 4 2002
Delivered-To: freebsd-questions@freebsd.org
Received: from mta6.snfc21.pbi.net (mta6.snfc21.pbi.net [206.13.28.240])
	by hub.freebsd.org (Postfix) with ESMTP id 8A86737B402
	for <freebsd-questions@freebsd.org>; Fri, 11 Jan 2002 12:35:02 -0800 (PST)
Received: from blackbox.pacbell.net ([64.166.86.36])
 by mta6.snfc21.pbi.net (iPlanet Messaging Server 5.1 (built May  7 2001))
 with ESMTP id <0GPS005PXJUCK2@mta6.snfc21.pbi.net> for
 freebsd-questions@freebsd.org; Fri, 11 Jan 2002 12:35:01 -0800 (PST)
Received: (from mikem@localhost)	by blackbox.pacbell.net (8.11.6/8.11.6)
 id g0BKZOx91746; Fri, 11 Jan 2002 12:35:24 -0800 (PST envelope-from mikem)
Date: Fri, 11 Jan 2002 12:35:24 -0800
From: Mike Makonnen <mike_makonnen@yahoo.com>
Subject: Re: Sylpheed dumps core when starting
In-reply-to: <20020111083808.L62722-100000@trittico.fiddi.com>
To: Dave Runkle <dave@runkle.com>
Cc: freebsd-questions@freebsd.org
Message-id: <200201112035.g0BKZOx91746@blackbox.pacbell.net>
MIME-version: 1.0
X-Mailer: Sylpheed version 0.6.5 (GTK+ 1.2.10; i386--freebsd5.0)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
References: <20020111182500.60804342.sdg@rila.bg>
 <20020111083808.L62722-100000@trittico.fiddi.com>
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

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