Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org, Hui Zhu <hui_zhu@mentor.com>
Subject: Re: [RFC] Autoload-breakpoints new version [3/9] notification async
Date: Tue, 14 Aug 2012 12:01:00 -0000	[thread overview]
Message-ID: <CANFwon0h9uSMHBHGfEoFHJBhCqSy-0MMd-L-pG8EUcFjn+_+1Q@mail.gmail.com> (raw)
In-Reply-To: <50286552.1090003@codesourcery.com>

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


  reply	other threads:[~2012-08-14 12:01 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 [this message]
2012-08-15 14:23         ` Hui Zhu
2012-08-23 10:44           ` Hui Zhu
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=CANFwon0h9uSMHBHGfEoFHJBhCqSy-0MMd-L-pG8EUcFjn+_+1Q@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=hui_zhu@mentor.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