Message-Id:	<m0zIc0a-000S4JC@inti.gov.ar>
Comments:	Authenticated sender is <salvador AT natacha DOT inti DOT gov DOT ar>
From:	"Salvador Eduardo Tropea (SET)" <salvador AT inti DOT gov DOT ar>
Organization:	INTI
To:	Gautier DOT DeMontmollin AT maths DOT unine DOT ch, djgpp AT delorie DOT com
Date:	Mon, 14 Sep 1998 14:04:53 +0000
MIME-Version:	1.0
Subject:	Re: Trace-back with details
In-reply-to:	<uLZNdSuR0FTf@nedcu4>

Gautier DOT DeMontmollin AT maths DOT unine DOT ch wrote:

> Are there means to include an explicit trace-back
> into the run-time code, that would use the symbol
> table to explain the EIPs ?
> 
> The idea would be to obtain the trace-back info
> directly when an error occurs - without running
> symify or re-running from gdb.

Eli proposed it some time ago but it didn't have too much fans. I don't 
think that's a good idea because you must supply executables with debug 
information to the users, and that's a big waste of disk.
My editor is 3.5 Mb long (using a patched as to avoid extra symbols,
avoiding stabs+ and using no-debug version of TVision) but the compressed exe 
is 420Kb (with UPX 0.30). So I distribute the editor without debug info and 
keep a copy of the released version in my hard disk. If a user gets a SIGSEGV 
s/he just need to send the trace-back (the editor stores this information in 
a safe place) and I run symify in my machine.
As this situation is the most common the idea of an "autosymify" wasn't 
implemented. But I think Eli have an example code.

SET
------------------------------------ 0 --------------------------------
Visit my home page: http://set-soft.home.ml.org/
or
http://www.geocities.com/SiliconValley/Vista/6552/
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Alternative e-mail: set-soft AT usa DOT net set AT computer DOT org
ICQ: 2951574
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA
TE: +(541) 759 0013

- Raw text -