Date:	Wed, 24 Apr 1996 23:52:42 +0800 (GMT+0800)
From:	Orlando Andico <orly AT abigail DOT eee DOT upd DOT edu DOT ph>
To:	Jeffrey Taylor <elric AT wheel DOT dcn DOT davis DOT ca DOT us>
cc:	djgpp AT delorie DOT com
Subject:	Re: Standard 32-bit libraries
In-Reply-To:	<4lliee$4ig@mark.ucdavis.edu>
Message-ID:	<Pine.LNX.3.91.960424234705.197A-100000@abigail.eee.upd.edu.ph>
MIME-Version:	1.0

On 24 Apr 1996, Jeffrey Taylor wrote:

> I debug across multiple source files in mutliple directories.  What is 
> the difficulty?  Or did I miss a winky?
> 

Tell me how!!! (if...)
Here's what I do: I keep code in my header files (not nice, I admit, but 
I do it...) I compile the program, I run GDB. I want the execution to 
stop somewhere in some header file, so (ex. main.c and header.h) I say 
something like:

break header.h:345

I use this crapper all the time under linux, sunos and solaris, but it 
don't work with djgpp. Also, let's say I have a function whose code is in 
header.h, and I want to trace through it, so I say:

break my_function

GDB swallows this nicely, but when the thread hits the function, it says 
something like

break in main.c, line XXX
         ^^^^^^
then complains that line XXX isn't in main.c (something like, main.c has
only 20 lines, but XXX=100). I think GDB thinks that your main program and
all headers can be catenated into one huge mass... messy. Eli suggested
that I do just that -- cat everything into one huge mass, debug it like
so, then chop it up again when I'm done. Ick. 

That's what I mean about not being able to debug multiple source files. 
If you can do it, I'd *love* your dropping me a hint.

Thanks,

Orlando Andico
orly AT abigail DOT eee DOT upd DOT edu DOT ph

- Raw text -