Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: daviddoria <daviddoria@gmail.com>, gdb@sourceware.org
Subject: Re: Don't step into STL
Date: Sat, 24 Jan 2009 21:46:00 -0000	[thread overview]
Message-ID: <8ac60eac0901241346o783b2030odc4a6a5f37adfd0f@mail.gmail.com> (raw)
In-Reply-To: <18811.34794.239283.316635@kahikatea.snap.net.nz>

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


  reply	other threads:[~2009-01-24 21:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-24 21:04 daviddoria
2009-01-24 21:28 ` Nick Roberts
2009-01-24 21:46   ` Paul Pluzhnikov [this message]
2009-01-24 22:57     ` daviddoria

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8ac60eac0901241346o783b2030odc4a6a5f37adfd0f@mail.gmail.com \
    --to=ppluzhnikov@google.com \
    --cc=daviddoria@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=nickrob@snap.net.nz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox