From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] -data-list-changed-registers (Take 2)
Date: Mon, 13 Jun 2005 04:47:00 -0000 [thread overview]
Message-ID: <17069.4116.293354.462840@farnswood.snap.net.nz> (raw)
In-Reply-To: <20050613024022.GB9288@nevyn.them.org>
> It looks like you're doing basically mi_out_rewind. There's already
> several of these in captured_mi_execute_command. They don't catch this
> because throw_exception takes us past them, all the way back to
> mi_execute_command.
>
> If we add an mi_out_rewind call right here:
> 1176 /* The command execution failed and error() was called
> 1177 somewhere */
>
> Then the problem goes away.
So, basically, it just needed one line fix! Hmm...I think I'll look at the
rest of the MI code before I start re-inventing it again.
From mi_cmd_data_list_register_values, I removed:
if (!target_has_registers)
{
mi_error_message = xstrprintf ("mi_cmd_data_list_register_values: No registers.");
return MI_CMD_ERROR;
}
Why do you think it should stay?
Nick
next prev parent reply other threads:[~2005-06-13 4:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-01 11:12 [PATCH] -data-list-changed-registers Nick Roberts
2005-06-03 19:13 ` Daniel Jacobowitz
2005-06-03 22:35 ` Nick Roberts
2005-06-03 22:36 ` Daniel Jacobowitz
2005-06-04 11:41 ` Nick Roberts
2005-06-06 20:44 ` Nick Roberts
2005-06-11 5:54 ` Nick Roberts
2005-06-11 6:50 ` [PATCH] -data-list-changed-registers (Take 2) Nick Roberts
2005-06-13 2:40 ` Daniel Jacobowitz
2005-06-13 4:47 ` Nick Roberts [this message]
2005-06-13 13:48 ` Daniel Jacobowitz
2005-06-13 22:38 ` Nick Roberts
2005-06-13 22:42 ` Daniel Jacobowitz
2005-06-14 2:45 ` Nick Roberts
2005-06-17 1:51 ` Daniel Jacobowitz
2005-06-17 3:13 ` Nick Roberts
2005-06-17 3:22 ` Daniel Jacobowitz
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=17069.4116.293354.462840@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.org \
--cc=gdb-patches@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