public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net To: gdb-testers@sourceware.org Subject: [binutils-gdb] testsuite: Restore gdb_is_target_remote_prompt Date: Wed, 28 Feb 2018 14:13:00 -0000 [thread overview] Message-ID: <3083294d65393a31522586e058500f6abda29b83@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 3083294d65393a31522586e058500f6abda29b83 *** Author: Simon Marchi <simon.marchi@ericsson.com> Branch: master Commit: 3083294d65393a31522586e058500f6abda29b83 testsuite: Restore gdb_is_target_remote_prompt In patch Add test for load command 3275ef477498e0500d7ea440f1bc51787acf4610 I removed gdb_is_target_remote_prompt, but did not realize it was used in mi_is_target_remote. This makes the gdb.mi/mi-nonstop.exp crash, for example: ERROR: (DejaGnu) proc "gdb_is_target_remote_prompt {[(]gdb[)] }" does not exist. The error code is TCL LOOKUP COMMAND gdb_is_target_remote_prompt The info on the error is: invalid command name "gdb_is_target_remote_prompt" while executing "::tcl_unknown gdb_is_target_remote_prompt {[(]gdb[)] }" ("uplevel" body line 1) invoked from within "uplevel 1 ::tcl_unknown $args" This patch restores it. gdb/testsuite/ChangeLog: * lib/gdb.exp (gdb_is_target_1): Add prompt_regexp parameter and use it. (gdb_is_target_remote_prompt): New proc. (gdb_is_target_remote): Use gdb_is_target_remote_prompt. (gdb_is_target_native): Pass prompt parameter to gdb_is_target_1.
next reply other threads:[~2018-02-28 14:13 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-02-28 14:13 sergiodj+buildbot [this message] 2018-02-28 14:13 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot 2018-02-28 14:19 ` Failures on Fedora-i686, " sergiodj+buildbot 2018-02-28 14:23 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2018-02-28 14:23 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2018-02-28 14:34 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2018-02-28 14:37 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-02-28 14:46 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-02-28 14:52 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2018-02-28 14:53 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2018-02-28 15:18 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2018-03-01 1:18 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-03-01 1:44 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
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=3083294d65393a31522586e058500f6abda29b83@gdb-build \ --to=sergiodj+buildbot@sergiodj.net \ --cc=gdb-testers@sourceware.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: linkBe 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).