From: Michael Chastain <mec.gnu@mindspring.com>
To: jack.bloch@siemens.com, gdb@sources.redhat.com
Cc: rafael.benitez@siemens.com
Subject: Re: Breakpoint in object destructor
Date: Wed, 04 Aug 2004 13:50:00 -0000 [thread overview]
Message-ID: <4110E9A7.nailCLA11Q0R1@mindspring.com> (raw)
In-Reply-To: <7A25937D23A1E64C8E93CB4A50509C2A0310F2F0@stca204a.bus.sc.rolm.com>
"Bloch, Jack" <jack.bloch@siemens.com> wrote:
> We are trying to set a breakpoint in a destructor. this does not seem to
> work. Running GDB 5.1.1 on a SuSE 2.4 Kernel. The breakpoint gets set, but
> it never fires.
>
What compiler are you using to build the program that you are compiling?
If you are using gcc 3.X, this is a known, unfixed problem.
See the PROBLEMS file in a recent release of gdb (like gdb 6.2)
for an explanation. Briefly: gcc 3.X emits two or three object code
functions for each destructor; gdb doesn't understand this;
so gdb puts a breakpoint in just one copy.
Michael C
next prev parent reply other threads:[~2004-08-04 13:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 12:05 Bloch, Jack
2004-08-04 13:50 ` Michael Chastain [this message]
2004-08-04 13:53 Bloch, Jack
2004-08-04 14:38 ` Michael Chastain
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=4110E9A7.nailCLA11Q0R1@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=gdb@sources.redhat.com \
--cc=jack.bloch@siemens.com \
--cc=rafael.benitez@siemens.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