X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
From: "Gerrit van Niekerk" <gerritvn AT gpvno DOT co DOT za>
Organization: GPvNO
To: simnav AT gmail DOT com, djgpp AT delorie DOT com
Date: Mon, 28 Jan 2008 21:46:09 +0200
MIME-Version: 1.0
Subject: Re: Question about traceback with no debug info
Message-ID: <479E4D21.17893.11CE4684@gerritvn.gpvno.co.za>
In-reply-to: <be948131-d3b5-4c97-816c-356d21294f24@d4g2000prg.googlegroups.com>
References: <be948131-d3b5-4c97-816c-356d21294f24 AT d4g2000prg DOT googlegroups DOT com>
X-mailer: Pegasus Mail for Windows (4.41)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On 28 Jan 2008 at 7:43, simnav AT gmail DOT com wrote:

> Having the source code used to compile a software with no debugging
> information in the executable, is it possible to know the position in
> source where a SIGSEGV signal is raised, only using the call frame
> traceback ? If yes... how ?

Yes, but you will have to compile the source code with symbolic 
debugging (-g). Then you can run symify giving the image with symbols 
as an argument even if the stripped image was run when the SIGSEGV 
happened.