Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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 22:38:00 -0000	[thread overview]
Message-ID: <17070.2773.135064.388886@farnswood.snap.net.nz> (raw)
In-Reply-To: <20050613134759.GA7102@nevyn.them.org>

 > > 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?
 > 
 > Cuz it was late and I wasn't paying a great deal of attention to your
 > patch, once I figured out the mi_out_rewind problem.  In the interest
 > of uniformity, let's remove it.  Could you (test and) commit the
 > obvious patch?

Committed.

I get many failures on the testsuite, I'll try to move to a newer PC/kernel.
mi-regs.exp seems OK though.

I would like to commit my changes to -var-update (2005-05-02) sometime.

I have also removed a large number of annotations from my working copy.
Andrew started this process, it would be nice if he can be involved but
maybe thats not possible. There are a lot of changes to the following files:

gdb/ada-valprint.c
gdb/annotate.c
gdb/annotate.h
gdb/blockframe.c
gdb/breakpoint.c
gdb/cp-valprint.c
gdb/event-top.c
gdb/frame.c
gdb/infrun.c
gdb/interps.c
gdb/jv-valprint.c
gdb/p-valprint.c
gdb/printcmd.c
gdb/stack.c
gdb/utils.c
gdb/valprint.c

Is anyone interested?  It would be good to do this now as a release doesn't
seem to be imminent.

Nick


2005-06-14  Nick Roberts  <nickrob@snap.net.nz>

	* mi/mi-main.c (mi_cmd_data_list_register_values): Remove test for
	registers now that mi_execute_command rewinds after an error.


*** /home/nick/src/gdb/mi/mi-main.c.~1.79~	2005-06-14 10:37:18.000000000 +1200
--- /home/nick/src/gdb/mi/mi-main.c	2005-06-14 09:18:08.000000000 +1200
***************
*** 433,444 ****
  
    format = (int) argv[0][0];
  
-   if (!target_has_registers)
-     {
-       mi_error_message = xstrprintf ("mi_cmd_data_list_register_values: No registers.");
-       return MI_CMD_ERROR;
-     }
- 
    list_cleanup = make_cleanup_ui_out_list_begin_end (uiout, "register-values");
  
    if (argc == 1)		/* No args, beside the format: do all the regs */
--- 433,438 ----


  reply	other threads:[~2005-06-13 22:38 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
2005-06-13 13:48                 ` Daniel Jacobowitz
2005-06-13 22:38                   ` Nick Roberts [this message]
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=17070.2773.135064.388886@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