Date:	Tue, 20 Jul 1999 12:00:51 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Richard Dawe <richdawe AT bigfoot DOT com>
cc:	DJGPP newsgroup <djgpp AT delorie DOT com>
Subject:	Re: Bizarre debugging format problem
In-Reply-To:	<379249F0.D17518C@tudor21.net>
Message-ID:	<Pine.SUN.3.91.990720120029.4115H-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Sun, 18 Jul 1999, Richard Dawe wrote:

> Commands:
>     l main
> 
> This returned something like 'no line information for main'.

Bizarre, indeed...

> BTW this only seems to have happened since I upgraded to gcc 2.8.1.

Well, I never upgraded to 2.8.1, since it has so many bugs.  This
might explain why I never saw anything like what you describe.  So I
cannot even try compiling the program you posted.

Here's what I suggest to do:

Modify your program so that it pauses at some point, e.g. by calling
`getch', and when it does, interrupt it with Ctrl-BREAK.  Then run
SYMIFY and see if it reports source line numbers.  If it does, then
the problem is in GDB, and perhaps the latest version of GDB solves
that.  I can let let you download the latest binary of GDB 4.18 that
I'm using, to see whether it does any better; or I can try it myself
if you tell me where can I download the binary of your terst program.

> So my solution is to use one of -gstabs, -gstabs+, -ggdb. -gstabs doesn't
> use any gdb extensions, so I'll use that.

I understand that stabs solved the problem.

- Raw text -