From: Yao Qi <yao@codesourcery.com>
To: Pedro Alves <palves@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH v4 0/14] Run all-stop on non-stop target
Date: Thu, 10 May 2012 12:09:00 -0000 [thread overview]
Message-ID: <4FABAFB3.2000503@codesourcery.com> (raw)
In-Reply-To: <4FAAAD6C.1010507@redhat.com>
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 (é½å°§)
next prev parent reply other threads:[~2012-05-10 12:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 13:12 Yao Qi
2012-05-03 13:12 ` [PATCH 03/14] Change parameters of adjust_pc_after_break Yao Qi
2012-05-03 13:12 ` [PATCH 01/14] Fix displaced stepping debug log Yao Qi
2012-05-03 15:01 ` Pedro Alves
2012-05-03 13:13 ` [PATCH 08/14] Uninstall infrun_async_inferior_event token in remote target Yao Qi
2012-05-03 13:13 ` [PATCH 09/14] Set thread's state in infcall Yao Qi
2012-05-03 13:13 ` [PATCH 12/14] manythreads.exp: Adjust to handle threads appearing/disappearing after "Program received signal SIGFOO" Yao Qi
2012-05-03 13:13 ` [PATCH 05/14] Support in linux-nat target Yao Qi
2012-05-03 13:13 ` [PATCH 10/14] watchthreads-reorder.exp: Don't assume there is no infrun output after prompt Yao Qi
2012-05-03 13:13 ` [PATCH 14/14] kfail gdb/13858 Yao Qi
2012-05-03 13:13 ` [PATCH 11/14] Fix fails in gdb.trace/pending.exp Yao Qi
2012-05-03 13:13 ` [PATCH 07/14] Support in remote target Yao Qi
2012-05-03 13:13 ` [PATCH 06/14] Flip to set target-async on by default and NEWS Yao Qi
2012-05-03 13:13 ` [PATCH 02/14] Move displaced_step_fixup bits out to displaced_step_next Yao Qi
2012-05-03 13:13 ` [PATCH 13/14] ia64-sigill.exp: Don't assume there's no infrun output after the prompt Yao Qi
2012-05-03 13:14 ` [PATCH 04/14] Run all-stop on non-stop Yao Qi
2012-05-03 14:23 ` [PATCH v4 0/14] Run all-stop on non-stop target Pedro Alves
2012-05-03 14:38 ` Yao Qi
2012-05-09 17:46 ` Pedro Alves
2012-05-10 12:09 ` Yao Qi [this message]
2012-05-10 14:21 ` Pedro Alves
2012-05-26 11:08 ` Yao Qi
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=4FABAFB3.2000503@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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