From: Yao Qi <qiyaoltc@gmail.com>
To: John Baldwin <jhb@FreeBSD.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v3] Add a 'starti' command.
Date: Fri, 03 Nov 2017 13:00:00 -0000 [thread overview]
Message-ID: <86inerwm8t.fsf@gmail.com> (raw)
In-Reply-To: <20170911220803.73819-1-jhb@FreeBSD.org> (John Baldwin's message of "Mon, 11 Sep 2017 15:08:03 -0700")
John Baldwin <jhb@FreeBSD.org> writes:
> +# Continue to the start of main(). The constructor should have run so
> +# 'x' should be 1.
> +
> +gdb_breakpoint main
> +gdb_test_sequence "continue" "" {
> + "\\$2 = 1"
> + ".*Breakpoint .*main \\(\\) at .*starti.c.*"
Here is a test failure, captured by buildbot,
https://sourceware.org/ml/gdb-testers/2017-q3/msg04381.html
(gdb) gdb_expect_list pattern: /\$2 = 1/
continue^M
Continuing.^M
$2 = 1^M
gdb_expect_list pattern: /.*Breakpoint .*main \(\) at .*starti.c.*/
^M
Breakpoint 1, Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_unwinders function is missing: ^M
main () at /home/yao/SourceCode/gnu/gdb/git/gdb/testsuite/gdb.base/starti.c:29^M
29 return 0;^M
(gdb) gdb_expect_list pattern: //
FAIL: gdb.base/starti.exp: continue (pattern 3 + sentinel) (timeout)
Can you take a look?
--
Yao (齐尧)
next prev parent reply other threads:[~2017-11-03 13:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 22:08 John Baldwin
2017-09-18 23:15 ` John Baldwin
2017-09-19 14:35 ` Pedro Alves
2017-09-19 18:23 ` John Baldwin
2017-09-19 18:29 ` Pedro Alves
2017-11-03 13:00 ` Yao Qi [this message]
2017-11-15 20:11 ` John Baldwin
2017-11-15 20:23 ` Pedro Alves
2017-11-15 23:32 ` John Baldwin
2017-11-16 10:54 ` Pedro Alves
2017-11-16 12:38 ` [pushed] Fix gdb.base/starti.exp racy test (Re: [PATCH v3] Add a 'starti' command.) Pedro Alves
2017-11-16 18:00 ` John Baldwin
2017-11-16 18:15 ` Pedro Alves
2017-11-16 9:55 ` [PATCH v3] Add a 'starti' command 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=86inerwm8t.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=jhb@FreeBSD.org \
/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