Re: [PATCH v4 0/14] Run all-stop on non-stop target

Yao Qi
2012-05-10T12:09:09Z

On 05/10/2012 01:46 AM, Pedro Alves wrote:
> I see this in sync vs async:
>
> PASS: gdb.python/py-finish-breakpoint.exp: set FinishBreakpoint with default frame value
> PASS: gdb.python/py-finish-breakpoint.exp: set FinishBreakpoint
> PASS: gdb.python/py-finish-breakpoint.exp: check return_value at init
> -PASS: gdb.python/py-finish-breakpoint.exp: check MyFinishBreakpoint hit
> -PASS: gdb.python/py-finish-breakpoint.exp: check return_value
> -PASS: gdb.python/py-finish-breakpoint.exp: check finishBP on default frame has been hit
> -PASS: gdb.python/py-finish-breakpoint.exp: ensure that finish bp is invalid afer normal hit
> -PASS: gdb.python/py-finish-breakpoint.exp: return to main()
> -PASS: gdb.python/py-finish-breakpoint.exp: check FinishBP not allowed in main
> +FAIL: gdb.python/py-finish-breakpoint.exp: check MyFinishBreakpoint hit (GDB internal error)
> +ERROR: Could not resync from internal error (timeout)
> +UNRESOLVED: gdb.python/py-finish-breakpoint.exp: check return_value (timeout)
> +ERROR: Process no longer exists
> +UNRESOLVED: gdb.python/py-finish-breakpoint.exp: check finishBP on default frame has been hit
> +ERROR: Couldn't send python print finishbp.is_valid() to GDB.
> +UNRESOLVED: gdb.python/py-finish-breakpoint.exp: ensure that finish bp is invalid afer normal hit
> +ERROR: Couldn't send finish to GDB.
> +UNRESOLVED: gdb.python/py-finish-breakpoint.exp: return to main()
> +ERROR: Couldn't send python MyFinishBreakpoint (None, gdb.selected_frame ()) to GDB.
> +UNRESOLVED: gdb.python/py-finish-breakpoint.exp: check FinishBP not allowed in main
>
> Do you see it too?
>

Yes, I saw them as well on both native gdb and remote. This is the last
set problems of on async.

> I looked at this a couple months ago, but didn't make much progress. I'll try to
> figure it out next.

Thanks for looking at these issues, Pedro.

--
Yao (é½å°§)