Sender: nate AT cartsys DOT com
Message-ID: <3710F751.AC818698@cartsys.com>
Date: Sun, 11 Apr 1999 12:26:09 -0700
From: Nate Eldredge <nate AT cartsys DOT com>
X-Mailer: Mozilla 4.08 [en] (X11; I; Linux 2.2.5 i586)
MIME-Version: 1.0
To: djgpp AT delorie DOT com
Subject: Re: RHIDE question: Tracing into multiple source files...
References: <7emuf8$g9v$1 AT news1 DOT rmi DOT net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com

David Whitcombe wrote:
> 
> Is it RHIDE or is it me?
> 
> If I've got, say, BLOBTYPE.HPP, which is including BLOBTYPE.CC,
> and then, in my main file, Totally_Excellent_Blobulator.CPP, I include
> BLOBTYPE.HPP, with the class definitions and everything.
> 
> But something is wrong with class blobtype! It's not deallocating properly
> or something, and I want to trace into it.
> 
> In Rhide, the cursor just drops to the last close curly brace and waits
> while the code
> gets stepped through.
> 
> Is it stepping through the other file, and if I had it open, I could see it?
> 
> Usually, when I have to debug a class, I just paste the whole monster
> into whatever file I'm working on, tinker with it, and paste it back, but it
> would be very nice if I could just trace into separate source files.

It's a limitation of the standard DJGPP COFF debugging format; it can't
properly represent included files.  GCC 2.8.1 and above support the
stabs format, however, which can.  Try compiling with the `-gstabs'
option (RHIDE may even have an option for this).
-- 

Nate Eldredge
nate AT cartsys DOT com