Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Daniel Simard" <Daniel.Simard@simplernetworks.com>
To: <gdb@sources.redhat.com>
Subject: The step over function of gdb enters header file code
Date: Mon, 07 Feb 2005 13:49:00 -0000	[thread overview]
Message-ID: <23BEE0D8F55D0747A13EFE0A6937FFA11B4B@simnet.simplernetworks.com> (raw)

Hi, 

I am not sure if it is the right place to post those kings of questions, but if it is not please tell me where to post it.

I am trying to debug an existing module that is using STL (string, vector etc...). When I break it the code, I want to trace it using the "step over" command of gdb, the debugger continually enters and break into STL header file code. I know that those header files are using template, but is it possible to tell gdb to not trace into system code when using "step over" command. I tried kdevelop and ddd debuggers and both are doing the same thing. My version of gdb is 6.1.

Thanks
___________________
Daniel-Olivier Simard, eng. 
Firmware Designer 
Simpler Networks Inc.
1840 TransCanada, Suite 100 
Dorval, Québec, Canada, H9P 1H7
Phone : (514) 684-2112 x354 
Fax : (514) 684-2127



             reply	other threads:[~2005-02-07 13:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-07 13:49 Daniel Simard [this message]
2005-02-07 15:10 ` Kris Warkentin

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=23BEE0D8F55D0747A13EFE0A6937FFA11B4B@simnet.simplernetworks.com \
    --to=daniel.simard@simplernetworks.com \
    --cc=gdb@sources.redhat.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