From: Tom Tromey <tromey@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/3] New test case for PR12929.
Date: Tue, 30 Jul 2013 19:49:00 -0000 [thread overview]
Message-ID: <87a9l3ltft.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1337939766-1579-2-git-send-email-yao@codesourcery.com> (Yao Qi's message of "Fri, 25 May 2012 17:56:04 +0800")
>>>>> "Yao" == Yao Qi <yao@codesourcery.com> writes:
Yao> * gdb.python/py-sync-interp.c: New.
Yao> * gdb.python/py-sync-interp.exp: New.
Yao> +# This test case is copied from PR14135.
Yao> +# http://sourceware.org/bugzilla/show_bug.cgi?id=14135
Yao> +
Yao> +set testfile "py-sync-interp"
Yao> +set srcfile ${testfile}.c
Yao> +set binfile ${objdir}/${subdir}/${testfile}
standard_testfile
Yao> +# Test command 'where' is executed when command 'attach' is done, otherwise
Yao> +# function 'sleep' may not show up in backtrace.
Yao> +
Yao> +gdb_test_sequence "python gdb.execute(\"attach $testpid\"); gdb.execute(\"where\")" \
Yao> + "attach and where" {
Yao> + "\[\r\n\]#.* in sleep \\(\\) "
Yao> + "\[\r\n\]#.* in foo1 \\(\\) at "
Yao> + "\[\r\n\]#.* in foo2 \\(\\) at "
Yao> + "\[\r\n\]#.* in foo3 \\(\\) at "
Yao> + "\[\r\n\]#.* in main \\(\\) at "
Yao> +}
I applied this patch to my branch, to see what would happen. On my
system (x86-64 Fedora 18, with glibc debuginfo installed), I see this
backtrace in the log:
python gdb.execute("attach 11985"); gdb.execute("where")
0x0000003e422bb4e0 in __nanosleep_nocancel () at ../sysdeps/unix/syscall-template.S:81
81 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
#0 0x0000003e422bb4e0 in __nanosleep_nocancel () at ../sysdeps/unix/syscall-template.S:81
#1 0x0000003e422bb3a1 in __sleep (seconds=0) at ../sysdeps/unix/sysv/linux/sleep.c:137
#2 0x00000000004005da in foo1 () at ../../../archer/gdb/testsuite/gdb.python/py-sync-interp.c:26
#3 0x00000000004005e5 in foo2 () at ../../../archer/gdb/testsuite/gdb.python/py-sync-interp.c:32
#4 0x00000000004005f0 in foo3 () at ../../../archer/gdb/testsuite/gdb.python/py-sync-interp.c:38
#5 0x00000000004005fb in main () at ../../../archer/gdb/testsuite/gdb.python/py-sync-interp.c:45
This yielded a FAIL:
FAIL: gdb.python/py-sync-interp.exp: attach and where (pattern 1)
Tom
next prev parent reply other threads:[~2013-07-30 19:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 9:56 Fix PR14135 Yao Qi
2012-05-25 9:56 ` [PATCH 2/3] Don't force interpreter sync mode in execute_gdb_command Yao Qi
2013-07-30 19:55 ` Tom Tromey
2013-07-30 20:13 ` Tom Tromey
2012-05-25 9:56 ` [PATCH 3/3] Match output in async mode Yao Qi
2013-07-30 20:06 ` Tom Tromey
2013-07-31 7:45 ` Yao Qi
2012-05-25 9:56 ` [PATCH 1/3] New test case for PR12929 Yao Qi
2013-07-30 19:49 ` Tom Tromey [this message]
2013-07-30 20:11 ` Tom Tromey
2013-07-31 7:53 ` Yao Qi
2013-07-31 15:19 ` Tom Tromey
2013-08-01 6:39 ` Yao Qi
2012-07-17 2:51 ` Fix PR14135 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=87a9l3ltft.fsf@fleche.redhat.com \
--to=tromey@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