From: Roland McGrath <roland@redhat.com>
To: gdb@sources.redhat.com
Subject: gdb.threads/linux-dp.exp test nit
Date: Sun, 17 Aug 2003 22:05:00 -0000 [thread overview]
Message-ID: <200308172205.h7HM53i19437@magilla.sf.frob.com> (raw)
The test suite will produce:
FAIL: gdb.threads/linux-dp.exp: first thread-specific breakpoint hit
if you have debugging information for libpthread available. That is:
gdb_test "where" "print_philosopher.*philosopher.* from .*libpthread.*" \
"first thread-specific breakpoint hit"
It expects the backtrace to say "something () from libpthread.so.0" for the
frames indicating the callers in libpthread of print_philosopher. But my
backtrace looks like this:
#0 print_philosopher (n=3, left=33 '!', right=33 '!') at /home/roland/BUILD/gdb
+dejagnu-5.3.90_20030710/gdb/testsuite/gdb.threads/linux-dp.c:105
#1 0x08048aa3 in philosopher (data=0x804a094) at /home/roland/BUILD/gdb+dejagnu
-5.3.90_20030710/gdb/testsuite/gdb.threads/linux-dp.c:148
#2 0x4001c9ea in start_thread (arg=0x21) at pthread_create.c:264
#3 0x40136247 in clone () from /lib/tls/libc.so.6
The crucial line is #2, where it has source info instead of "from
libpthread". The assumption that the backtrace will look either of these
ways is bogus anyway. The threads implementation could well produce a
backtrace that didn't show a recognizable frame before `philosopher'. If
the intent of this test predicate is to make sure it's in the right thread,
it really ought to be looking at the N argument to print_philosopher in the
backtrace.
Thanks,
Roland
reply other threads:[~2003-08-17 22:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200308172205.h7HM53i19437@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=gdb@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).