From: Yao Qi <yao@codesourcery.com>
To: Pedro Alves <palves@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 4/4] gdb: kfail for PR14161
Date: Thu, 14 Jun 2012 15:01:00 -0000 [thread overview]
Message-ID: <201206142301.34598.yao@codesourcery.com> (raw)
In-Reply-To: <4FD76C4E.20107@redhat.com>
On Wednesday 13 June 2012 00:20:30 Pedro Alves wrote:
> > + # 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.
I use "remote_file target delete" in the new patch when "is_remote target" is
true, otherwise use tcl builtin command to remove files.
gdb/testsuite:
2012-06-14 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 | 14 +++++++++++++-
1 files changed, 13 insertions(+), 1 deletions(-)
diff --git a/gdb/testsuite/gdb.trace/strace.exp b/gdb/testsuite/gdb.trace/strace.exp
index b96ab41..1520055 100644
--- a/gdb/testsuite/gdb.trace/strace.exp
+++ b/gdb/testsuite/gdb.trace/strace.exp
@@ -100,6 +100,10 @@ proc strace_remove_socket { action } {
sleep 5
+ if { ![is_remote target] && ! [string equal $action "detach"] } {
+ setup_kfail gdb/14161 *-*-*
+ }
+
set test "socket file removed"
if [is_remote target] {
set status [remote_exec target "sh -c \"exit `\\\[ -S $socket_file ]`\""]
@@ -332,7 +336,15 @@ 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.
+ if [is_remote target] {
+ foreach match [glob -nocomplain "/tmp/gdb_ust*"] {
+ remote_file target delete $match
+ }
+ } else {
+ eval file delete [glob "/tmp/gdb_ust*"]
+ }
return
}
if { ![gdb_target_supports_trace] } then {
--
1.7.0.4
next prev parent reply other threads:[~2012-06-14 15:01 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 4/4] gdb: kfail for PR14161 Yao Qi
2012-06-12 16:21 ` Pedro Alves
2012-06-14 15:01 ` Yao Qi [this message]
2012-06-15 19:33 ` Pedro Alves
2012-06-20 13:55 ` Yao Qi
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-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=201206142301.34598.yao@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