From: Hui Zhu <teawater@gmail.com>
To: Marc Khouzam <marc.khouzam@ericsson.com>,
Michael Snyder <msnyder@vmware.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] Patch to fix "reverse-step" command error
Date: Tue, 09 Jun 2009 02:18:00 -0000 [thread overview]
Message-ID: <daef60380906081918i34c549e8j7295e1abba24957c@mail.gmail.com> (raw)
In-Reply-To: <daef60380905110007j4796811es152f943e86f318fe@mail.gmail.com>
PING
On Mon, May 11, 2009 at 15:07, Hui Zhu<teawater@gmail.com> wrote:
> PING
>
> On Wed, May 6, 2009 at 16:13, Hui Zhu <teawater@gmail.com> wrote:
>> Hi Marc and Michael,
>>
>> Sorry I forget this issue just reproduce in SLED 10.
>>
>> I reproduced it with cvs-head and patch can fix it. Michael, Please
>> help me review it.
>>
>> The attachment is the new patch follow cvs-head.
>>
>> 2009-05-06 Hui Zhu <teawater@gmail.com>
>>
>> * infrun.c (handle_inferior_event): Make inferior insert
>> breakpoint at right address or step in reverse and it stepped
>> into dynsym resolve code.
>>
>> Thanks,
>> Hui
>>
>> On Wed, May 6, 2009 at 13:31, Hui Zhu <teawater@gmail.com> wrote:
>>> Hi Marc,
>>>
>>> I cannot reproduce this issue with cvs-head.
>>> Could you please help me test with this issue?
>>> If both of us cannot reproduce this issue, I think I can give up this patch.
>>>
>>> Thanks,
>>> Hui
>>>
>>>
>>> On Mon, Mar 2, 2009 at 14:10, teawater <teawater@gmail.com> wrote:
>>>> Hi Michael,
>>>>
>>>> This patch is for bug in
>>>> http://sourceware.org/ml/gdb-patches/2009-02/msg00246.html.
>>>>
>>>> The reason of bug is when inferior reverse exection into dynsym
>>>> resolve code, gdb doesn't insert breakpoint in right address.
>>>> It just happen in some distributions for example SLED.
>>>>
>>>> This patch make gdb insert breakpoint in right address or step in that case.
>>>>
>>>> 2008-03-02 Hui Zhu <teawater@gmail.com>
>>>>
>>>> * infrun.c (handle_inferior_event): Make inferior insert
>>>> breakpoint at right address or step in reverse and it stepped
>>>> into dynsym resolve code.
>>>>
>>>> Thanks,
>>>> Hui
>>>>
>>>
>>
>
next prev parent reply other threads:[~2009-06-09 2:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 6:10 teawater
2009-05-06 5:31 ` Hui Zhu
2009-05-06 8:13 ` Hui Zhu
2009-05-11 7:07 ` Hui Zhu
2009-06-09 2:18 ` Hui Zhu [this message]
2009-06-21 23:12 ` Michael Snyder
2009-06-22 1:52 ` Marc Khouzam
2009-06-22 2:18 ` Hui Zhu
2009-06-22 3:46 ` Michael Snyder
-- strict thread matches above, loose matches on Subject: below --
2009-03-02 6:06 teawater
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=daef60380906081918i34c549e8j7295e1abba24957c@mail.gmail.com \
--to=teawater@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=marc.khouzam@ericsson.com \
--cc=msnyder@vmware.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