Date: Thu, 7 Dec 2000 13:59:09 -0500
Message-Id: <200012071859.NAA05800@envy.delorie.com>
X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp-workers AT delorie DOT com
In-reply-to: <NBBBIOJKJBNCHJBEKHLOAEDGCCAA.tim.van.holder@pandora.be>
Subject: Re: DJGPP linker script update
References:  <NBBBIOJKJBNCHJBEKHLOAEDGCCAA DOT tim DOT van DOT holder AT pandora DOT be>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


Part of the problem is that unwinding a call stack often takes more
work than a generic bfd utility provides.  For the djgpp case, the
stack is pretty simple, but MIPS for example doesn't always have a
frame pointer - you MUST decode the debug information (dwarf2, for
example) to unwind the stack.  GDB already knows how to do this.

In fact, building djgpp programs with -fomit-frame-pointer would cause
this problem also; gdb with dwarf2 could unwind it but nobody else
could.