Date: Tue, 27 Feb 1996 17:58:29 -0800 (GMT)
From: Orlando Andico <oandico AT eee DOT upd DOT edu DOT ph>
To: j DOT aldrich6 AT genie DOT com
cc: djgpp AT delorie DOT com
Subject: Re: I love GDB
In-Reply-To: <199602270648.AA203403712@relay1.geis.com>
Message-ID: <Pine.SOL.3.91.960227174853.3630A-100000@gollum>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 27 Feb 1996 j DOT aldrich6 AT genie DOT com wrote:

> 
> I have since dramatically increased the size of the buffers, so this problem
> should never plague me again.  I would like to thank the designers of GDB for
> making this wonderful tool.  :)
> 
> John
> 

thank you John. However, I did post something about a bug(?) in GDB (at 
least, in the version for DJGPP/MS-DOS). I inclose it, to wit:

> Is there something wrong with my GDB?
> I want to set a breakpoint in a header file, not the main C program. So I 
> say something like:
>
>     break video.h:138
>
> (which seems to be the correct invocation, says the holy Info). GDB 
> replies, "no source file named video.h" (even though I'm *sure* my main 
> program includes this header).
>
> So, I decide to set the breakpoint in the *function* included in the 
> header file, like so:
>
>    break init_driver
>
> So GDB replies, "Breakpoint 1 at 0x1bbe: file rtdsp.c, line 138." 
> (although it really should be file video.h, line 138). Ok, I run the 
> program. GDB says: "Breakpoint 1, init_driver (vector=128) at rtdsp.c:138 
> Line number 138 out of range; rtdsp.c has 66 lines.
>
> So what gives?
>

I have determined that this problem does *not* appear under Linux, only 
with the GDB I'm using with V2. Someone has written me that this is a 
probable *known bug* with GDB; but Linux works fine...

If you know how to fix this problem, I'd much appreciate your dropping me 
a hint. Unless of course, you just want to inflict me with Linux envy. ;)

Thanks!

Orly