From: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
To: <djgpp-workers AT delorie DOT com>
Subject: RE: DJGPP linker script update
Date: Thu, 7 Dec 2000 18:38:17 +0100
Message-ID: <NBBBIOJKJBNCHJBEKHLOAEDGCCAA.tim.van.holder@pandora.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-reply-to: <Pine.LNX.4.10.10012071653470.18292-100000@acp3bf>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id MAA07422
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

> >  2. If the latter, do we have a volunteer to add core file support at 
> >     least for GNU/Linux? ;-)
> 
> That would probably be a reinvention of a wheel that already exists inside
> either BFD or GDB.
I don't think so. If core files are accessed through bfd, adding reading of
core files to bfdsymify would be fairly trivial. Creating a stack backtrace
from the core file might be slightly less trivial. Of course, I admit I no
far too little about the internals of \(bfd\|gdb\|\(bfd\)?symify\) to speak
with any kind of authority on the matter.