From: Richard Dawe Newsgroups: comp.os.msdos.djgpp Subject: Re: symify problem Date: Wed, 16 Oct 2002 17:03:30 +0100 Lines: 24 Message-ID: <3DAD8DD2.A632564D@phekda.freeserve.co.uk> References: <3DAD80B7 DOT 98C390C1 AT cyberoptics DOT com> NNTP-Posting-Host: 62.136.41.87 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: news8.svr.pol.co.uk 1034788820 14074 62.136.41.87 (16 Oct 2002 17:20:20 GMT) NNTP-Posting-Date: 16 Oct 2002 17:20:20 GMT X-Complaints-To: abuse AT theplanet DOT net X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.19 i586) X-Accept-Language: de,fr To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Hello. Eric Rudd wrote: > I have used symify for many years without a problem, but lately I have > been having problems getting line numbers in a traceback. [snip] > As you can see, symify gives me the subroutine names and offsets, but > no line numbers. I don't know what I'm doing wrong -- this used to > work. Is this a new problem that was introduced in gcc v3.2? I'm > using a symify.exe dated 2001-12-24 (in the latest DJDEV203). I dimly > recall that there was some way of getting an annotated assembly listing > that included the offsets of the line numbers, but either I can't > remember how to do that, or it doesn't work anymore. What should I do > next to isolate this problem? I think -g defaults to DWARF-2 debugging information with gcc 3.x. Try explicitly building it with COFF debugging information, using -gcoff instead of -g. I just tried it with your test program and it worked for me (gcc 3.2, binutils 2.13). HTH, regards, -- Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]