From: Daniel Jacobowitz <drow@false.org>
To: Brian Budge <brian.budge@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: breakpoints and symbol examination problems
Date: Tue, 11 Mar 2008 00:37:00 -0000 [thread overview]
Message-ID: <20080311003238.GA14908@caradoc.them.org> (raw)
In-Reply-To: <5b7094580803101705m7bc6e8ffqa480a74d9b0ab548@mail.gmail.com>
On Mon, Mar 10, 2008 at 05:05:17PM -0700, Brian Budge wrote:
> Hi all -
>
> I'm having an issue with reaching breakpoints and examining symbols in
> my C++ code via gdb. I can set breakpoints in my .cpp files and
> actually reach these, but if I put breakpoints in included header
> files (in template code), my program will run right through the
> breakpoints.
Try a snapshot of the current CVS HEAD or the 6.8 branch. This should
be fixed.
> Additionally, I can't seem to examine any "stack" variables once in
> these template functions. I can see member variables, global
> variables, and function parameters.
This may be fixed, or it may be a compiler bug. GCC is not very good
about emitting local variable information in optimized code.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-03-11 0:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 0:33 Brian Budge
2008-03-11 0:37 ` Daniel Jacobowitz [this message]
2008-03-11 9:53 ` Michael Snyder
2008-03-11 17:45 ` Brian Budge
2008-03-11 21:32 ` Brian Budge
2008-03-12 9:14 ` Brian Budge
[not found] ` <5b7094580803121306v7da4475dy5f91be7c7d8753e0@mail.gmail.com>
2008-03-12 22:31 ` Fwd: " Brian Budge
2008-03-12 23:02 ` Brian Budge
2008-03-13 3:56 ` Daniel Jacobowitz
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=20080311003238.GA14908@caradoc.them.org \
--to=drow@false.org \
--cc=brian.budge@gmail.com \
--cc=gdb@sourceware.org \
/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