Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: mweglicki8208 <mweglicki@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: GDB steping into STL Headers.
Date: Thu, 11 Feb 2010 02:26:00 -0000	[thread overview]
Message-ID: <daef60381002101826o5979d1eaxef1e91ccd3ec629c@mail.gmail.com> (raw)
In-Reply-To: <27535106.post@talk.nabble.com>

Try next?

On Thu, Feb 11, 2010 at 01:38, mweglicki8208 <mweglicki@gmail.com> wrote:
>
> Hello,
>
> Is there a way to disable stepping into a STL headers? This is what is
> happening:
>
> std::string test = "New string";
>
>
> And i have a lot of calls from stl headers like:
> (gdb) step
> 671
> /opt/gcc/linux64/ix86/gcc_3.4.5-2p2/lib/gcc/x86_64-redhat-linux/3.4.5/../../../../include/c++/3.4.5/bits/stl_list.h:
> No
>        in
> /opt/gcc/linux64/ix86/gcc_3.4.5-2p2/lib/gcc/x86_64-redhat-linux/3.4.5/../../../../include/c++/3.4.5/bits/stl_list.h
>
>
> Is it possible to void it? So for example next will allways step into next
> line of code that i wish to debug?
> --
> View this message in context: http://old.nabble.com/GDB-steping-into-STL-Headers.-tp27535106p27535106.html
> Sent from the Sourceware - gdb list mailing list archive at Nabble.com.
>
>


  reply	other threads:[~2010-02-11  2:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-10 17:38 mweglicki8208
2010-02-11  2:26 ` Hui Zhu [this message]
2010-02-11  6:22 ` mweglicki8208
2010-02-11  9:28   ` Obtaining number of children of a dynamic varobj Elmenthaler, Jens
2010-02-11 17:23     ` Vladimir Prus
2010-02-11 17:56   ` GDB steping into STL Headers Tom Tromey
2010-02-11 19:03     ` Jim Ingham
2010-02-11 19:09       ` Daniel Jacobowitz
2010-02-11 19:12         ` Jim Ingham
2010-02-12  9:32           ` mweglicki8208
2010-02-12 10:43             ` Christophe-Marie Duquesne

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=daef60381002101826o5979d1eaxef1e91ccd3ec629c@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=mweglicki@gmail.com \
    /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