Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 4/4] gdb: kfail for PR14161
Date: Tue, 12 Jun 2012 16:21:00 -0000	[thread overview]
Message-ID: <4FD76C4E.20107@redhat.com> (raw)
In-Reply-To: <1339246002-1987-5-git-send-email-yao@codesourcery.com>

On 06/09/2012 01:46 PM, Yao Qi wrote:

> GDB doesn't have something equivalent to pause_all/unpause_all in GDBserver,
> so GDB is unable to control the threads correctly after sending commands
> to agent.


Yeah, my ideal would be to merge gdb/gdbserver's backends, but you've been
distracting me from that goal.  ;-)

>  KFAIL this first.



> gdb/testsuite:
> 
> 2012-06-09  Yao Qi  <yao@codesourcery.com>
> 
> 	KFAIL for PR14161.
> 	* gdb.trace/strace.exp (strace_remove_socket): kfail for native.
> 	Cleanup socket files.
> ---
>  gdb/testsuite/gdb.trace/strace.exp |   11 +++++++++++
>  1 files changed, 11 insertions(+), 0 deletions(-)
> 
> diff --git a/gdb/testsuite/gdb.trace/strace.exp b/gdb/testsuite/gdb.trace/strace.exp
> index f141e9b..00a3fad 100644
> --- a/gdb/testsuite/gdb.trace/strace.exp
> +++ b/gdb/testsuite/gdb.trace/strace.exp
> @@ -92,6 +92,10 @@ proc strace_remove_socket { action } {
>  
>      sleep 2
>  
> +    if { ![is_remote target] && ! [string equal $action "detach"] } {
> +	setup_kfail gdb/14161 *-*-*
> +    }
> +
>      set test "socket file removed"
>      if { [file exists $socket_file] } {
>  	fail $test
> @@ -318,6 +322,13 @@ if { ![is_remote target]
>      strace_remove_socket "quit"
>      strace_remove_socket "detach"
>      strace_remove_socket "continue"
> +
> +    # Due to PR gdb/14161, sockets files are not removed when agent exists.

> +    # However this problem only affects native gdb, so we don't have to bother

> +    # 'remote_file target delete'.  Simple tcl command 'file delete' should
> +    # be OK.
> +    eval file delete [glob "/tmp/gdb_ust*"]
> +


"bother with".  But note this doesn't work with remote host testing.

>      return
>  }
>  



-- 
Pedro Alves


  reply	other threads:[~2012-06-12 16:21 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-09 12:47 [PATCH 0/4] PR14161: a partial fix Yao Qi
2012-06-09 12:47 ` [PATCH 1/4] New test for removing socket file in gdb.trace/strace.exp Yao Qi
2012-06-12 14:51   ` Pedro Alves
2012-06-14 14:39     ` Yao Qi
2012-06-15 19:00       ` Pedro Alves
2012-06-20 13:46         ` Yao Qi
2012-06-21 15:56           ` Pedro Alves
2012-06-27  3:55             ` Yao Qi
2012-06-09 12:47 ` [PATCH 2/4] Remove socket file at exit Yao Qi
2012-06-12 15:14   ` Pedro Alves
2012-06-14 14:44     ` Yao Qi
2012-06-15 19:02       ` Pedro Alves
2012-06-09 12:47 ` [PATCH 3/4] New agent command 'kill' and used by gdbserver Yao Qi
2012-06-09 13:11   ` Eli Zaretskii
2012-06-12 16:14   ` Pedro Alves
2012-06-14 14:50     ` Yao Qi
2012-06-14 16:37       ` Eli Zaretskii
2012-06-15 19:25       ` Pedro Alves
2012-06-20 13:49         ` Yao Qi
2012-06-21 16:05           ` Pedro Alves
2012-06-09 12:47 ` [PATCH 4/4] gdb: kfail for PR14161 Yao Qi
2012-06-12 16:21   ` Pedro Alves [this message]
2012-06-14 15:01     ` Yao Qi
2012-06-15 19:33       ` Pedro Alves
2012-06-20 13:55         ` Yao Qi
2012-07-27  8:19 ` [committed] : [PATCH 0/4] PR14161: a partial fix 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=4FD76C4E.20107@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --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