X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; format=flowed; charset=iso-8859-1; reply-type=original
Message-id: <012d01c861d2$6aea8540$0100a8c0@broadpark.no>
From: Gisle Vanem <gvanem AT broadpark DOT no>
To: djgpp AT delorie DOT com
References: <be948131-d3b5-4c97-816c-356d21294f24 AT d4g2000prg DOT googlegroups DOT com>
Subject: Re: Question about traceback with no debug info
Date: Mon, 28 Jan 2008 18:22:54 +0100
X-Priority: 3
X-MSMail-priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Reply-To: djgpp AT delorie DOT com

<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 ?

Not the source-lines, but the EIP etc. at time of signal. Look at function 
except_handler() in sock_ini.c in the Watt-32 [1] sources for an example.

[1] http://www.bgnett.no/~giva/watt32s-2.2-dev.10.zip

--gv