Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: paawan oza <paawan1982@yahoo.com>
Cc: gdb@sourceware.org
Subject: Re: reversible debugging, enhancements, proposals
Date: Fri, 15 Oct 2010 18:22:00 -0000	[thread overview]
Message-ID: <m37hhj5nb7.fsf@fleche.redhat.com> (raw)
In-Reply-To: <717587.85098.qm@web112501.mail.gq1.yahoo.com> (paawan oza's	message of "Fri, 15 Oct 2010 02:30:47 -0700 (PDT)")

>>>>> ">" == paawan oza <paawan1982@yahoo.com> writes:

>> 1) if we want to debug the long linked list chain, we need to to move
>> manually next, next, and so on...  so if you want to to see 100th
>> node's value, or want to know cerain field's value in all
>> nodes.... (there also could be level of nesting in the list also,

>> for e.g. list->some_field->next and so on...) then it becomes
>> cumbersome and difficult.  I am not sure whether that facility is
>> available, but I think it is a very useful feature, if it is not
>> there.

>> I would like to make a patch which gives that facility in gdb.

It is simple to write things like this in Python.

You can write a pretty-printer, which is nice for application- or
library-specific cases.  E.g., libstdc++ has a std::list printer that
does this.

Or, you could write a new command that is more general purpose.

Tom


  parent reply	other threads:[~2010-10-15 18:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-15  9:31 paawan oza
2010-10-15 13:15 ` Jan Kratochvil
2010-10-15 13:49   ` paawan oza
2010-10-15 15:18     ` Jan Kratochvil
2010-10-15 17:43       ` paawan oza
2010-10-15 18:22 ` Tom Tromey [this message]
2010-10-16  8:03 paawan oza

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=m37hhj5nb7.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=paawan1982@yahoo.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