From: Niko Sams <niko.sams@gmail.com>
To: gdb <gdb@sourceware.org>
Subject: Re: -stack-list-locals and children
Date: Mon, 29 Jun 2009 09:36:00 -0000 [thread overview]
Message-ID: <629542d40906290236t2b879f1w7c6f4a4a558cd0ac@mail.gmail.com> (raw)
In-Reply-To: <h29voq$ari$1@ger.gmane.org>
On Mon, Jun 29, 2009 at 10:59, Vladimir Prus<vladimir@codesourcery.com> wrote:
> André Pönitz wrote:
>
>> On Sunday 28 June 2009 21:03:01 Niko Sams wrote:
>>> Hi,
>>>
>>> -stack-list-locals doesn't return an numchild element. How can the IDE
>>> know if a local
>>> is has children?
>>>
>>> If there are children, they are listed in value:
>>> ^done,locals=[{name="list",value="QList = {[0] = \"hello\"}"}]
>>>
>>> Is it a good idea to parse the value with an regular expression to
>>> find out if there are children?
>>
>> It would be really nice if 'type' and 'numchild' information was directly
>> included in that "primary" output. The information is available on
>> the gdb side, so parsing it from the 'value' field does not really look
>> like a good solution in the long run.
>
> As I mention in other email, getting the number of children is in general
> impossible. Maybe, "has_children" flag would be more appropriate -- this
> is somewhat more likely to be computable.
pretty printers could have an additional method to get numchild directly
without iterating over them.
But for a Tree-View has_children would be enough of course.
> I am not sure it was you, but there was an IRC discussion about making
> -stack-list-locals also print type of things -- can you describe exactly
> how you gonna use that information, so that I have a chance to implement
> that properly?
We don't show a type column in KDevelop, but for example QtCreator does.
Niko
prev parent reply other threads:[~2009-06-29 9:36 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
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 [this message]
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=629542d40906290236t2b879f1w7c6f4a4a558cd0ac@mail.gmail.com \
--to=niko.sams@gmail.com \
--cc=gdb@sourceware.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox