From: nickrob@snap.net.nz (Nick Roberts)
To: Niko Sams <niko.sams@gmail.com>
Cc: gdb <gdb@sourceware.org>
Subject: Re: -stack-list-locals and children
Date: Mon, 29 Jun 2009 11:49:00 -0000 [thread overview]
Message-ID: <19016.43585.442474.558778@totara.tehura.co.nz> (raw)
In-Reply-To: <629542d40906290230n4da6f347s1566847defb9a1c0@mail.gmail.com>
> > Also, is -stack-list-locals any better here? I'd expect it to either have
> > exactly the same performance problems, or ignore pretty-printing. If it
> > is considerably faster while still reporting 1000 children, it's performance
> > bug somewhere.
> It's much faster. I get about 100 children in the value followed by ....
I think the limit is 200 (show print elements) but if elements repeat themselves
(generally 0) an ellipsis is used.
Presumably it's much faster because -stack-list-locals just prints/dumps out the
values while variable objects allow you to edit, change format, expand, list
changed values etc...
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2009-06-29 11:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-28 19:03 Niko Sams
2009-06-28 19:31 ` Vladimir Prus
2009-06-28 19:56 ` Niko Sams
2009-06-29 5:26 ` Vladimir Prus
2009-06-29 7:13 ` Niko Sams
[not found] ` <629542d40906290012p33c5504pde20ddcd7da3474a@mail.gmail.com>
2009-06-29 8:18 ` Vladimir Prus
2009-06-29 9:30 ` Niko Sams
2009-06-29 9:45 ` Vladimir Prus
2009-06-29 11:49 ` Nick Roberts [this message]
2009-06-29 7:42 ` André Pönitz
2009-06-29 8:13 ` Nick Roberts
2009-06-29 8:37 ` André Pönitz
2009-06-29 9:33 ` Niko Sams
2009-06-30 10:14 ` Nick Roberts
2009-06-29 15:34 ` Pawel Piech
2009-06-29 16:40 ` Vladimir Prus
2009-06-29 16:55 ` Vladimir Prus
2009-06-29 22:46 ` Nick Roberts
2009-06-29 23:07 ` Pawel Piech
2009-06-30 3:26 ` Pawel Piech
2009-06-29 8:59 ` Vladimir Prus
2009-06-29 9:32 ` André Pönitz
2009-06-29 9:39 ` Vladimir Prus
2009-06-29 10:13 ` André Pönitz
2009-06-30 9:42 ` Vladimir Prus
2009-06-29 9:36 ` Niko Sams
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=19016.43585.442474.558778@totara.tehura.co.nz \
--to=nickrob@snap.net.nz \
--cc=gdb@sourceware.org \
--cc=niko.sams@gmail.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