From: Hui Zhu <teawater@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org, Hui Zhu <hui_zhu@mentor.com>,
Yao Qi <yao@codesourcery.com>
Subject: Re: [RFC] Autoload-breakpoints new version [3/9] notification async
Date: Thu, 23 Aug 2012 10:44:00 -0000 [thread overview]
Message-ID: <CANFwon1Hpt=crqzQQOfen3FNrntpvjFj8UrRXNVjW3cs=aH81Q@mail.gmail.com> (raw)
In-Reply-To: <CANFwon1XhnmWaqmxyhCgtHjNPM9rYAoUDPAfMZFkENJ-UgzVuA@mail.gmail.com>
On Wed, Aug 15, 2012 at 10:22 PM, Hui Zhu <teawater@gmail.com> wrote:
> On Tue, Aug 14, 2012 at 8:01 PM, Hui Zhu <teawater@gmail.com> wrote:
>> On Mon, Aug 13, 2012 at 10:24 AM, Yao Qi <yao@codesourcery.com> wrote:
>>> On 08/11/2012 11:19 PM, Hui Zhu wrote:
>>>>>
>>>>> >
>>>>> >I applied patch 1/9 and 3/9, and get following regressions in gdbserver
>>>>> > with
>>>>> >async mode on.
>>>>> >
>>>>> > FAIL: gdb.mi/mi-nonstop-exit.exp: finished exec continue (unknown
>>>>> > output
>>>>> >after running)
>>>>> > FAIL: gdb.mi/mi-nonstop-exit.exp: finished exec continue (2) (unknown
>>>>> > output
>>>>> >after running)
>>>>> > FAIL: gdb.mi/mi-nsmoribund.exp: resume all, waiting for program exit
>>>>> >(timeout)
>>>>
>>>> My part is OK, Could you tell me how do you do the test?
>>>>
>>>
>>> In gdb build dir, add the following line into testsuite/site.exp
>>>
>>> set GDBFLAGS "-ex \"set target-async on\""
>>>
>>> make check RUNTESTFLAGS="--target_board=native-gdbserver"
>>>
>>> or you can set GDBFLAGS in your own board file other than testuite/site.exp.
>>>
>>> --
>>> Yao
>>
>> Hi guys,
>>
>> I found this issue is because notification "Stop:" cannot be handled
>> in async handler.
>> What I thought is push it back a buffer and let GDB handle it later
>> that GDB in right status to handle it.
>>
>> I didn't have other good idea on this issue is because I cannot
>> reproduce it in command line.
>>
>> Do you have some comments on this issue?
>>
>> Thanks,
>> Hui
>
> Hi,
>
> I done a new version to handle this issue.
> Because readchar will throw error and pop_target directly in remote.c.
> So I change it use another way to handle it. Not sure it is good or
> not. But it make test can be passed.
>
> Thanks,
> Hui
Hi Pedro,
You reviewed the prev version of this patch that named report-async.
Now, I gived up the report-async and just extend the notification for
the function.
So could you help me with it? Thanks a lot.
Best,
Hui
next prev parent reply other threads:[~2012-08-23 10:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 7:10 Hui Zhu
2012-08-08 13:26 ` Yao Qi
2012-08-11 15:20 ` Hui Zhu
2012-08-13 2:25 ` Yao Qi
2012-08-14 12:01 ` Hui Zhu
2012-08-15 14:23 ` Hui Zhu
2012-08-23 10:44 ` Hui Zhu [this message]
2012-08-23 11:20 ` Pedro Alves
2012-08-23 12:46 ` Yao Qi
2012-08-23 14:30 ` Hui Zhu
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='CANFwon1Hpt=crqzQQOfen3FNrntpvjFj8UrRXNVjW3cs=aH81Q@mail.gmail.com' \
--to=teawater@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=hui_zhu@mentor.com \
--cc=palves@redhat.com \
--cc=yao@codesourcery.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