Date:	Thu, 17 Jun 1999 10:18:08 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Sanda AT 97 DOT gyarab DOT cz
cc:	djgpp AT delorie DOT com
Subject:	Re: iostream.cc
In-Reply-To:	<1209C942EC9@gyarab.cz>
Message-ID:	<Pine.SUN.3.91.990617101715.22717E-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Wed, 16 Jun 1999 Sanda AT 97 DOT gyarab DOT cz wrote:

> When i trace my cc programs, rhide gdb wants to trace into c++ 
> library, natably all cout and such operations. For this I need 
> iostream.cc which is nowhere to be found.

The sources of the C++ libraries are in v2gnu/lgp2811s.zip, available
from the same place you get DJGPP.  However, not that, to debug
library code, you will need to rebuild the libraries with debug info,
which might not be a simple task.

> Can anyone please tell me, 
> how can i force the debugger to skip over that lib or what archive is 
> iostream.cc in. I know i could F8skip the call, but the is not the 
> case with inline macro...:(

Are you sure?  I have never seen such problems with macros.  Perhaps
you mean inline functions, not macros?

Anyway, here are two ideas that might help:

  - use a temporary breakpoint instead of single-stepping: set such a
    breakpoint right AFTER the call to the inline code and let the
    code run until it hits the breakpoint;
  - use stabs debugging: compile and link your program with -gstabs+.
    The stabs debug info lifts many limitations of the default COFF
    debug info, including some problems with inlined code.

- Raw text -