* Don't step into STL
@ 2009-01-24 21:04 daviddoria
2009-01-24 21:28 ` Nick Roberts
0 siblings, 1 reply; 4+ messages in thread
From: daviddoria @ 2009-01-24 21:04 UTC (permalink / raw)
To: gdb
Is there anyway to set the debugger so when I "step into", it doesn't get
into crazy stuff (ie. vector.h) that I haven't written? Ie. only step into
until a step would step outside of files in my project?
Thanks,
Dave
--
View this message in context: http://www.nabble.com/Don%27t-step-into-STL-tp21645187p21645187.html
Sent from the Sourceware - gdb list mailing list archive at Nabble.com.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Don't step into STL
2009-01-24 21:04 Don't step into STL daviddoria
@ 2009-01-24 21:28 ` Nick Roberts
2009-01-24 21:46 ` Paul Pluzhnikov
0 siblings, 1 reply; 4+ messages in thread
From: Nick Roberts @ 2009-01-24 21:28 UTC (permalink / raw)
To: daviddoria; +Cc: gdb
> Is there anyway to set the debugger so when I "step into", it doesn't get
> into crazy stuff (ie. vector.h) that I haven't written? Ie. only step into
> until a step would step outside of files in my project?
I don't think so but it would be neat if GDB could be made to step into a
function when that line has debug information was available and over when it
wasn't.
--
Nick http://www.inet.net.nz/~nickrob
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Don't step into STL
2009-01-24 21:28 ` Nick Roberts
@ 2009-01-24 21:46 ` Paul Pluzhnikov
2009-01-24 22:57 ` daviddoria
0 siblings, 1 reply; 4+ messages in thread
From: Paul Pluzhnikov @ 2009-01-24 21:46 UTC (permalink / raw)
To: Nick Roberts; +Cc: daviddoria, gdb
On Sat, Jan 24, 2009 at 1:28 PM, Nick Roberts <nickrob@snap.net.nz> wrote:
> > Is there anyway to set the debugger so when I "step into", it doesn't get
> > into crazy stuff (ie. vector.h) that I haven't written?
How could GDB know what you have, and what you haven't written yet?
>> Ie. only step into
>> until a step would step outside of files in my project?
By the same token, GDB has no idea what constitutes your project,
and what doesn't.
> I don't think so but it would be neat if GDB could be made to step into a
> function when that line has debug information was available and over when it
> wasn't.
With STL templates, if your source is compiled with debug info, then any
STL you #include and use will have it as well.
There is an idea to implement a "step into the outermost function on current
line, without stepping into any functions used to set up parameters".
Will that address your actual needs?
Maybe it will get done this year ...
Cheers,
--
Paul Pluzhnikov
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Don't step into STL
2009-01-24 21:46 ` Paul Pluzhnikov
@ 2009-01-24 22:57 ` daviddoria
0 siblings, 0 replies; 4+ messages in thread
From: daviddoria @ 2009-01-24 22:57 UTC (permalink / raw)
To: gdb
Yea perfect - that's exactly what I want. Ok I'll just wait for the next
version :)
--
View this message in context: http://www.nabble.com/Don%27t-step-into-STL-tp21645187p21646286.html
Sent from the Sourceware - gdb list mailing list archive at Nabble.com.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2009-01-24 22:57 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-01-24 21:04 Don't step into STL daviddoria
2009-01-24 21:28 ` Nick Roberts
2009-01-24 21:46 ` Paul Pluzhnikov
2009-01-24 22:57 ` daviddoria
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox