On May 14, 2009, at 5:45 AM, Jerry Davis wrote:
> I have the following situation:
>
> I have a source file, which has a bunch of #includes which are .h
> files of the
> other classes used. I have full source. IOW, I can see in the
> source/ directory
> every .h and .C file of all the #includes.
>
> I use g++ to compile, and I compile with -g to make it debuggable
> with gdb. I
> am also new to gdb, but am learning.
>
> I hope you are with me so far.
>
> In my current source file, I instantiate an object of a class from
> another
> source file, which is #included in my current source file. When I
> use gdb, I
> can step into my current sources' functions and step through every
> line and
> print out variables etc. -- everything you would expect to do in a
> debugger,
> BUT, when I get to the method call of the other class object, I can
> do nothing
> but step OVER it.
>
> How do I compile it such that I can step INTO the other objects'
> method? and
> then step line by line in it? or do I have that capability already,
> and need to
> use some other command in gdb that I don't know about?
This is from old and unreliable memory but I think you have a path
problem. If memory serves, I resolved a similar problem by
rearranging my source hierarchy. I hope someone can give you a better
answer.
--
A young idea is a beautiful and a fragile thing. Attack people, not
ideas.
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)