From:	ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Debugging Information && SIGSEGV faults
Date:	11 Aug 1997 07:29:39 GMT
Organization:	The National Capital FreeNet
Lines:	22
Message-ID:	<5smf13$5lq@freenet-news.carleton.ca>
References:	<33ED6843 DOT 715EA2D8 AT NO_SPAMccds DOT cc DOT monash DOT edu>
Reply-To:	ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire)
NNTP-Posting-Host:	freenet3.carleton.ca
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Lyle (lpak1 AT NO_SPAMccds DOT cc DOT monash DOT edu) writes:
> Now heres, where the debugging info comes in. I can't seem to trace the
> program in gdb (or RHIDE for that matter, but then RHIDE dpends on gdb
> so that is to be expected). for some reason, i can only trace the code
> in the top source for each of my objects, ie
> I have object sources, and witihin those sources i have #include "sddsd"
> for some more code relating to that object. GDB doesn;t tract into any
> of the #include files, only the ones specified in the make file? Am i
> doing something wrong??

Well, debuggers don't trace into C++ functions in .h's because they're
inlined and have no separate existence as functions at run time. Move a
member function out of the .h into the .cc or .cpp file, that is causing
the problem, and you can then trace into it, and when you fix it, you can
move it back. (I learned this recently and the hard way by the way. :-))

--
    .*.  Where feelings are concerned, answers are rarely simple [GeneDeWeese]
 -()  <  When I go to the theater, I always go straight to the "bag and mix"
    `*'  bulk candy section...because variety is the spice of life... [me]
Paul Derbyshire ao950 AT freenet DOT carleton DOT ca, http://chat.carleton.ca/~pderbysh

- Raw text -