From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org, tromey@redhat.com
Subject: Re: RFC: fix bug with std::terminate handler
Date: Thu, 25 Feb 2010 18:26:00 -0000 [thread overview]
Message-ID: <201002251826.46359.pedro@codesourcery.com> (raw)
In-Reply-To: <m38wahrxr3.fsf@fleche.redhat.com>
On Thursday 25 February 2010 18:11:44, Tom Tromey wrote:
> call_function_by_hand installs a momentary breakpoint on std::terminate,
> and then deletes it later. However, this can cause a double deletion of
> the breakpoint. In the bug, the called function is dlopen, which causes
> gdb to enter solib_add, which calls breakpoint_re_set, deleting the
> momentary breakpoint.
Why doesn't stepping over "dlopen", with "(gdb) next" cause the
same problem with step-resume breakpoints?
--
Pedro Alves
next prev parent reply other threads:[~2010-02-25 18:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 18:11 Tom Tromey
2010-02-25 18:26 ` Pedro Alves [this message]
2010-02-25 19:19 ` Tom Tromey
2010-02-25 19:49 ` Pedro Alves
2010-02-26 1:52 ` Pedro Alves
2010-03-16 20:49 ` Tom Tromey
2010-03-25 18:14 ` Pedro Alves
2010-03-25 20:37 ` Tom Tromey
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=201002251826.46359.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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