From: Tom Tromey <tromey@redhat.com>
To: "Dave.Tian" <xhengdf@gmail.com>
Cc: gdb-patches@sourceware.org, Sergio Durigan Junior <sergiodj@redhat.com>
Subject: Re: [PATCH] bug fix for gdb 16039
Date: Thu, 17 Oct 2013 20:25:00 -0000 [thread overview]
Message-ID: <87sivztzkp.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAKjgB1OyrUtz9xqcqDSxEe72kDGEWBKy9LxZEkXDDd7RbX7y=A@mail.gmail.com> (Dave Tian's message of "Wed, 16 Oct 2013 01:44:15 -0500")
>>>>> ">" == Dave Tian <xhengdf@gmail.com> writes:
>> 1 Description: Gdb bug 16039 created by me
>> Title: Gdb next" command stop working when shared library unloaded.
>> Root Cause: There is "libc++" static linked into the shared library,
>> and since gdb insert internal breakpoints on std::terminate/longjump/...
>> so after dlclose, the memory address is
>> invalid,remove_breakpoints/insert_breakpoints
>> failed with EIO error.
The patch seems reasonable to me, but I think it would be good to have a
regression test for it.
Tom
next prev parent reply other threads:[~2013-10-17 20:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 2:18 Dave.Tian
2013-10-16 3:31 ` Sergio Durigan Junior
2013-10-16 6:44 ` Dave.Tian
2013-10-17 20:25 ` Tom Tromey [this message]
2013-10-19 4:38 ` Sergio Durigan Junior
2013-10-21 4:29 ` Dave.Tian
2013-10-28 23:33 ` Sergio Durigan Junior
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=87sivztzkp.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.com \
--cc=xhengdf@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