From: person AT hotmail DOT com
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Help needed with debugger
Message-ID: <384c9813.351625@news.camtech.net.au>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 991205125328 DOT 11787A-100000 AT is>
X-Newsreader: Forte Free Agent 1.11/32.235
Lines: 61
NNTP-Posting-Host: dialup-ad-14-58.camtech.net.au
X-Trace: ozemail.com.au 944543458 203.55.242.186 (Tue, 07 Dec 1999 16:10:58 EST)
NNTP-Posting-Date: Tue, 07 Dec 1999 16:10:58 EST
Organization: OzEmail Ltd, Australia
Distribution: world
Date: Tue, 07 Dec 1999 05:18:03 GMT
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

On Sun, 5 Dec 1999 12:54:25 +0200 (IST), Eli Zaretskii
<eliz AT is DOT elta DOT co DOT il> 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.  From what I understand of the trace
into debugging function, when you use the foo function in the main
listing the debugger should trace into this function by opening the
source and highlighting the next executable line of code when this
function is called (naturally fromt the main function).  When I use
the trace into function it does not open up the source code for any
called function, and thus the trace into function is much like the
step over function, which is no help @ all.  Can you help me?

BTW, I am not trying to set break points yet.

>On Sat, 4 Dec 1999 person AT hotmail DOT com wrote:
>
>> Can anyone help this guy/girl?
>
>It's probably best answered by someone who actually uses RHIDE's
>built-in debugger, but since nobody replied, I'll try.
>
>> >I'm trying to use the integrated debugger in RHIDE.  From what I
>> >understand, if you have source code in another file, which is used in
>> >your main file, and u use the trace into funciton, it should open up the
>> >source from that included file and read through it.
>
>What do you mean by ``included file''?  Did you actually use the
>#include directive to include it?  If so, please read section 12.8 of
>the DJGPP FAQ list.
>

Yes I did.  But I haven't set any breakpoints in the #included'd
source nor have I declared any inline functions, so I think this
doesn't apply to me.

>If you did NOT use #include, please explain more about your source.
>
>> >I have to redefine the folder in which
>> >the source code is kept, otherwise I get an error can not find
>> >main.cxx....
>
>I don't understand this.  What exactly do you mean by ``redefine the
>folder''?
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?)

Thanks anyway

Trent