From: Yao Qi <yao@codesourcery.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: <gdb-patches@sourceware.org>,
Sergio Durigan Junior <sergiodj@redhat.com>
Subject: Re: [patch] Fix TLS access for -static -pthread
Date: Thu, 05 Jun 2014 09:32:00 -0000 [thread overview]
Message-ID: <5390387C.7050308@codesourcery.com> (raw)
In-Reply-To: <20140605080639.GA32146@host2.jankratochvil.net>
On 06/05/2014 04:06 PM, Jan Kratochvil wrote:
>> This patch is to set another breakpoint at the end of main, so that
>> > main thread will hit it, and we can check the value of tlsvar then.
>> > It is safe and we don't have to worry about whether gdb is able to
>> > unwind from pthread library to main function or not.
> I have to warn that it may be a bit weaker test, it never tests both threads
> TLS access during the same stop, it tests only the current thread.
>
> But it still tests the patch works so I am fine with it (not an approval).
>
The patch below is to keep testing TLS access in one stop, and
work around the bug of unwinding clone. WDYT?
--
Yao (é½å°§)
Subject: [PATCH] Fix the race in gdb.threads/staticthreads.exp
The code in gdb.threads/staticthreads.exp about checking the value of
tlsvar in main thread is racy, because when child thread hits
breakpoint, the main thread may not go into pthread_join yet, and
may not be unwind to main.
This patch is to move the line setting breakpoint on after sem_wait,
so that the child thread will hit breakpoint after main thread calls
sem_post. IOW, when child thread hits breakpoint, the main thread is
in either sem_post or pthread_join. "up 10" can unwind main thread to
main.
gdb/testsuite:
2014-06-05 Yao Qi <yao@codesourcery.com>
* gdb.threads/staticthreads.c (thread_function): Move the line
setting breakpoint on forward.
* gdb.threads/staticthreads.exp: Update comments.
---
gdb/testsuite/gdb.threads/staticthreads.c | 2 +-
gdb/testsuite/gdb.threads/staticthreads.exp | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/gdb/testsuite/gdb.threads/staticthreads.c b/gdb/testsuite/gdb.threads/staticthreads.c
index 5c8eabe..db78063 100644
--- a/gdb/testsuite/gdb.threads/staticthreads.c
+++ b/gdb/testsuite/gdb.threads/staticthreads.c
@@ -38,7 +38,6 @@ thread_function (void *arg)
#ifdef HAVE_TLS
tlsvar = 2;
#endif
- printf ("Thread executing\n"); /* tlsvar-is-set */
while (sem_wait (&semaphore) != 0)
{
if (errno != EINTR)
@@ -47,6 +46,7 @@ thread_function (void *arg)
return NULL;
}
}
+ printf ("Thread executing\n"); /* tlsvar-is-set */
return NULL;
}
diff --git a/gdb/testsuite/gdb.threads/staticthreads.exp b/gdb/testsuite/gdb.threads/staticthreads.exp
index 9fa625a..bdc03d4 100644
--- a/gdb/testsuite/gdb.threads/staticthreads.exp
+++ b/gdb/testsuite/gdb.threads/staticthreads.exp
@@ -105,7 +105,7 @@ if { "$have_tls" != "" } {
gdb_continue_to_breakpoint "tlsvar-is-set" ".* tlsvar-is-set .*"
gdb_test "p tlsvar" " = 2" "tlsvar in thread"
gdb_test "thread 1" ".*"
- # Unwind from pthread_join.
+ # Unwind to main.
gdb_test "up 10" " in main .*"
gdb_test "p tlsvar" " = 1" "tlsvar in main"
}
--
1.9.0
next prev parent reply other threads:[~2014-06-05 9:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 11:52 Jan Kratochvil
2014-04-11 11:03 ` Jan Kratochvil
2014-05-20 15:10 ` Tom Tromey
2014-05-20 15:18 ` Jan Kratochvil
2014-05-20 15:10 ` Tom Tromey
2014-05-21 12:17 ` Jan Kratochvil
2014-05-21 14:14 ` Tom Tromey
2014-05-21 14:28 ` [commit] " Jan Kratochvil
2014-06-05 7:17 ` Yao Qi
2014-06-05 8:06 ` Jan Kratochvil
2014-06-05 9:32 ` Yao Qi [this message]
2014-06-05 9:39 ` Jan Kratochvil
2014-06-05 14:20 ` Yao Qi
2014-06-05 15:23 ` Pedro Alves
2014-06-06 2:26 ` Yao Qi
2014-06-05 15:18 ` Pedro Alves
2014-06-06 15:03 ` Jan Kratochvil
2014-06-06 2:36 ` Yao Qi
2014-06-06 6:16 ` Yao Qi
2014-06-06 14:20 ` Jan Kratochvil
2014-06-06 5:34 ` Sergio Durigan Junior
2014-06-06 14:21 ` Jan Kratochvil
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=5390387C.7050308@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=sergiodj@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