This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

step into next source line (that belongs to me)


Hi all,

When you need to trace a c++ constructor with multiple inheritages, you maybe 
want to 'step in' to a few of them, but not all.
What I am missing is a "step in"-alike that does only step to the very next 
line that is owned by my very own source code. Everything else is not of my 
interest and just blowes you up your mind when debugging and trying to 
understand.

The code to be "my very own" could be defined as all source files under a 
specified root directory. every debugging step that can be assigned to a file 
inside this (or one of these) root directories should be used as a step. 
every other lines (e.g. caused via big header files with lots of 
inlines/templates/etc.) should be stepped over and though ignored unless 
explicitely stated.

Is there a way to do such things using gdb?

Thanks in advance,
Christian Parpart.

Attachment: pgp00000.pgp
Description: PGP signature


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]