Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nick@nick.uklinux.net>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFC (gdb/mi): -stack-list-locals + PATCH
Date: Tue, 02 Dec 2003 03:14:00 -0000	[thread overview]
Message-ID: <16332.423.456414.834703@nick.uklinux.net> (raw)
In-Reply-To: <3FC3F85F.8050007@gnu.org>

 ...
 > > I don't really know what make_cleanup_ui_out_tuple_begin_end and do_cleanups
 > > do and I've approximated a simple data type to something that isn't
 > > TYPE_CODE_ARRAY or TYPE_CODE_STRUCT so it's probably a pretty gross hack.
 > > 
 > > The idea is that the user can see the value of simple data types immediately
 > > and can create variable objects for complex data types if he wishes to explore
 > > their values in more detail.
 > > 
 > > Any comments?
 > 
 > Looks like its time to cleanup "values" changing it to an enum or 
 > bitmask - too many magic numbers.

I see now that I've also inadvertantly defined "-stack-list-arguments 2". I don't
know what magic numbers are but clearly better structure is desirable.

 > Would is_integral_type() give you what you want?

For a simple data type? I don't think so. What about float? Perhaps I'm missing
your point.

 > 
 > For the cleanups try the restructured form:
 > 	{
 > 	  struct cleanup = cleanups = make_cleanup (NULL, null_cleanup);
 > 	  ..
 >            do_cleanups (cleanups);
 > 	}
 > http://sources.redhat.com/gdb/current/onlinedocs/gdbint_13.html#SEC112
 > 
 > make_cleanup_ui_out_tuple_begin_end opens the tuple and then closes it 
 > via a cleanup (if an error is thrown the tuple under construction is 
 > still finished).

I understand make_cleanup_ui_out_tuple_begin_end but not the above
restructured form. Do I have to call make_cleanup (or relatives) each time I
allocated memory i.e for each call to ui_out_field_stream?

While I'm thinking about the above, here is a basic patch for
mi-cmd-stack.c. Currently if -stack-list-locals is invoked then it gives a
segmentation fault (Segmentation fault (core dumped)). This is inconvenient
and the patch changes this to give an output similar to that of cli:

&"No frame selected.\n"
^error,msg="No frame selected."
(gdb) 


    Nick                                         http://www.nick.uklinux.net



*** mi-cmd-stack.c.~1.19.~      2003-06-12 23:29:37.000000000 +0100
--- mi-cmd-stack.c      2003-12-02 02:43:04.000000000 +0000
***************
*** 138,147 ****
--- 138,150 ----
  mi_cmd_stack_list_locals (char *command, char **argv, int argc)
  {
    if (argc != 1)
      error ("mi_cmd_stack_list_locals: Usage: PRINT_VALUES");
  
+   if (!deprecated_selected_frame)
+     error ("No frame selected.");
+ 
    list_args_or_locals (1, atoi (argv[0]), deprecated_selected_frame);
    return MI_CMD_DONE;
  }


  reply	other threads:[~2003-12-02  3:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-23  0:16 RFC (gdb/mi): -stack-list-locals Nick Roberts
2003-11-26  0:48 ` Andrew Cagney
2003-12-02  3:14   ` Nick Roberts [this message]
2003-12-09  2:42     ` RFC (gdb/mi): -stack-list-locals + REVISED PATCH Nick Roberts
2003-12-10 17:56       ` Andrew Cagney
2003-12-10 22:26         ` Jason Molenda
2003-12-12 20:51         ` RFC (gdb/mi): -stack-list-locals Nick Roberts
2003-12-12 21:09           ` David Carlton
2003-12-17  2:29             ` [PATCH: gdb/mi + doco] -stack-list-locals and -var-list-children Nick Roberts
2003-12-17  2:32               ` David Carlton
2003-12-17 18:51                 ` [PATCH: gdb/mi] -stack-list-locals Nick Roberts
2003-12-17 21:21                   ` David Carlton
2003-12-17 18:05               ` [PATCH: gdb/mi + doco] -stack-list-locals and -var-list-children Eli Zaretskii
2004-01-05 21:43               ` Andrew Cagney
2004-01-06  0:14                 ` [PATCH: gdb/mi] -stack-list-locals testcase Nick Roberts
2004-01-06  1:07                   ` Andrew Cagney
2004-01-07 16:31                     ` Andrew Cagney
2004-01-07 17:34                       ` Mark Kettenis
2004-01-07 17:40                         ` Daniel Jacobowitz
2003-12-12 23:01           ` RFC (gdb/mi): -stack-list-locals Jason Molenda

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=16332.423.456414.834703@nick.uklinux.net \
    --to=nick@nick.uklinux.net \
    --cc=cagney@gnu.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