This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFC] Autoload-breakpoints new version [3/9] notification async


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]