From: Patrick Palka <patrick@parcs.ath.cx>
To: Doug Evans <dje@google.com>
Cc: Keith Seitz <keiths@redhat.com>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: Several regressions and we branch soon.
Date: Tue, 23 Jun 2015 21:45:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.8.1506231742590.4322@idea> (raw)
In-Reply-To: <CADPb22RbcoyxPwwTTQCjSTdexN-D-gfWPd6doF2KbcMm074XyA@mail.gmail.com>
On Tue, 23 Jun 2015, Doug Evans wrote:
> On Tue, Jun 23, 2015 at 3:17 PM, Keith Seitz <keiths@redhat.com> wrote:
>> FWIW, I updated my virgin sandbox earlier, and I don't see a bunch of
>> the failures that you are/have. I've listed the ones I do see below.
>> FWIW, I have another branch that was last updated the first week of May
>> which shows none of these problems.
>>
>> I'll start looking at these failures immediately.
>>
>> Keith
>>
>> On 06/23/2015 12:03 PM, Doug Evans wrote:
>>
>>>>> FAIL: gdb.base/default.exp: info set
>>>>> FAIL: gdb.base/default.exp: show
The problem here seems to be that the "show" function corresponding to
the "mpx bound" command calls error("Intel(R) Memory Protection
Extensions not supported on this target."); which throws an exception
that causes the entire "info set"/"show" loop to exit early. Should
"show foo" ever throw an exception? Should the "info set"/"show" loop
expect an exception to be thrown from a show function?
This diff fixes the default.exp FAILs as far as I can tell:
diff --git a/gdb/i386-tdep.c b/gdb/i386-tdep.c
index 42d0346..d11efa1 100644
--- a/gdb/i386-tdep.c
+++ b/gdb/i386-tdep.c
@@ -8777,11 +8777,17 @@ i386_mpx_info_bounds (char *args, int from_tty)
struct type *data_ptr_type = builtin_type (gdbarch)->builtin_data_ptr;
if (!i386_mpx_enabled ())
- error (_("Intel(R) Memory Protection Extensions not\
- supported on this target."));
+ {
+ printf_unfiltered (_("Intel(R) Memory Protection Extensions not "
+ "supported on this target.\n"));
+ return;
+ }
if (args == NULL)
- error (_("Address of pointer variable expected."));
+ {
+ printf_unfiltered (_("Address of pointer variable expected.\n"));
+ return;
+ }
addr = parse_and_eval_address (args);
@@ -8856,7 +8862,7 @@ static struct cmd_list_element *mpx_set_cmdlist, *mpx_show_cmdlist;
static void
set_mpx_cmd (char *args, int from_tty)
{
- help_list (mpx_set_cmdlist, "set mpx", all_commands, gdb_stdout);
+ help_list (mpx_set_cmdlist, "set mpx ", all_commands, gdb_stdout);
}
/* Helper function for the CLI commands. */
@@ -8901,7 +8907,7 @@ is \"default\"."),
add_prefix_cmd ("mpx", class_support, set_mpx_cmd, _("\
Set Intel(R) Memory Protection Extensions specific variables."),
- &mpx_set_cmdlist, "set tdesc ",
+ &mpx_set_cmdlist, "set mpx ",
0 /* allow-unknown */, &setlist);
/* Add "mpx" prefix for the show commands. */
next prev parent reply other threads:[~2015-06-23 21:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 18:31 Doug Evans
2015-06-23 18:55 ` Patrick Palka
2015-06-23 19:03 ` Doug Evans
2015-06-23 20:17 ` Keith Seitz
2015-06-23 20:53 ` Doug Evans
2015-06-23 21:45 ` Patrick Palka [this message]
2015-06-24 11:55 ` Yao Qi
2015-06-25 16:35 ` Tedeschi, Walfred
2015-07-01 8:49 ` Yao Qi
[not found] ` <AC542571535E904D8E8ADAE745D60B1944445D44@IRSMSX104.ger.corp.intel.com>
2015-07-01 9:30 ` Walfred Tedeschi
2015-07-02 10:09 ` Yao Qi
2015-07-02 15:34 ` Yao Qi
2015-07-02 16:19 ` [PATCH] Don't throw an error in "show mpx bound" implementation Patrick Palka
2015-07-06 9:31 ` Yao Qi
2015-06-24 10:21 ` Several regressions and we branch soon Yao Qi
[not found] ` <87lhf8yz90.fsf@br87z6lw.de.ibm.com>
2015-06-25 13:34 ` Doug Evans
2015-06-25 18:00 ` Andreas Arnez
2015-06-30 15:21 ` Yao Qi
2015-06-30 18:09 ` Andreas Arnez
2015-07-01 8:01 ` Yao Qi
2015-07-10 9:33 ` Yao Qi
2015-07-10 16:12 ` Andreas Arnez
2015-07-10 16:23 ` Ulrich Weigand
2015-07-20 15:08 ` Andreas Arnez
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=alpine.DEB.2.20.8.1506231742590.4322@idea \
--to=patrick@parcs.ath.cx \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@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