Mail Archives: djgpp/1999/12/07/08:53:11
On Tue, 7 Dec 1999 person AT hotmail DOT com wrote:
> Okay, i've read the FAQ and it prob. does not solve my prob. Say you
> define a function, but the source of that function is in another file,
> say foo.hpp. You include this function in your main listing
> (main.cxx) by using #include.
Section 12.8 of the FAQ explains that this is a limitation of the COFF
debugging info, and suggests to compile with -gstabs+. Did you try that?
If not, please do.
> BTW, I am not trying to set break points yet.
It doesn't matter. Tracing into a functions involves a hidden breakpoint
being set behind the scenes by the debugger, in order to stop the program
when it enters the function into which you are tracing.
So what section 12.8 of the FAQ says does apply to your case.
> I think that the default directory where DJGPP looks for source code
> is the folder it was intalled in - ie: c:\djgpp. What I have found,
> is that if you try to compile source in a file not included in the
> folder DJGPP is installed in (c:/anyfolder), you have to add a search
> path so that it compiles and knows where to look for the source
> (options/directories/source). ie, you have to enter c:/anyfolder into
> the options so that it searches for your source file there. I was
> wondering if this might be related to the debugger not being able to
> find where my source is kept, and therefore I have to manually tell
> the debugger where to find my source code, so that the trace into
> function can open it (or something like that, do u understand?)
The COFF debug info doesn't include the directory of the source file,
only its name, so you MUST tell the debugger which directories to search.
I don't know off the top of my head if stabs debugging info includes
the directory, but after you compile with -gstabs+, you could see for
yourself if it solves this problem as well.
- Raw text -