all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 21438@debbugs.gnu.org
Subject: bug#21438: 25.0.50; GUD locals frame/window doesn't shows struct values as nil
Date: Wed, 09 Sep 2015 17:10:10 +0200	[thread overview]
Message-ID: <87y4gfljcd.fsf@gnu.org> (raw)
In-Reply-To: <83twr365of.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 09 Sep 2015 17:14:24 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> I guess the usage of --simple-values is intentional, and in fact, when
>> trying to use "--all-values" instead I get a
>> 
>>   error in process filter: gdb-jsonify-buffer: Stack overflow in regexp matcher
>
> Yes, the use of --simple-values is intentional.  If you want to see
> the values of the fields, you need to click mouse-2 on the variable
> name, and then Emacs will pop up a frame with the fields.

Yes, or I can watch the variable and get a nice speedbar tree view which
I can expand recursively.  Really nice!

>> I'm not actually sure if it would be benefitical to use --all-values
>> even if that regexp matching error was fixed because the structs can be
>> really large.  But at least the value should not be shown as "nil" but
>> as "<non-simple value>" or something else which makes it obvious that
>> the displayed value is not the real value.
>
> Like the patch below?  If you think it's OK, I will push it.

Yes, that's exactly what I had in mind.

Bye,
Tassilo





  reply	other threads:[~2015-09-09 15:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-09  6:04 bug#21438: 25.0.50; GUD locals frame/window doesn't shows struct values as nil Tassilo Horn
2015-09-09 14:14 ` Eli Zaretskii
2015-09-09 15:10   ` Tassilo Horn [this message]
2015-09-09 15:57     ` Eli Zaretskii

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=87y4gfljcd.fsf@gnu.org \
    --to=tsdh@gnu.org \
    --cc=21438@debbugs.gnu.org \
    --cc=eliz@gnu.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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.