Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: "Joel Borggrén-Franck" <joel.borggren.franck@gmail.com>
Cc: "André Pönitz" <andre.poenitz@nokia.com>, gdb@sourceware.org
Subject: Re: Python API questions and use cases
Date: Thu, 16 Sep 2010 19:11:00 -0000	[thread overview]
Message-ID: <m3wrqlpkpd.fsf@fleche.redhat.com> (raw)
In-Reply-To: <AANLkTinqU_uKORndRP7A8Ouy406TOb6WKz8y1eiOHDGP@mail.gmail.com>	("Joel =?utf-8?Q?Borggr=C3=A9n-Franck=22's?= message of "Thu, 16 Sep 2010 13:56:29	+0200")

>>>>> "Joel" == Joel Borggrén-Franck <joel.borggren.franck@gmail.com> writes:

Joel> This might be a case of missing (or obscure) documentation. Is there a
Joel> place (other than the C impl.) where I can find documentation for the
Joel> constructors/inits for the different gdb.XYZ types?

The gdb manual should have full documentation for the Python API.
I say "should" because we did find an undocumented method once, so it is
possible that there are others that we missed.  But by and large the
manual describes it all.

After seeing questions on the list for the last year or so, I would say
that the manual is weak either on examples or on a tutorial.  Perhaps we
should put some effort into one or the other.

Tom


  reply	other threads:[~2010-09-16 19:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-15 13:43 Joel Borggrén-Franck
2010-09-15 18:01 ` Tom Tromey
2010-09-15 19:04   ` Phil Muldoon
2010-09-16  6:13     ` Joel Borggrén-Franck
2010-09-16  7:33   ` Joel Borggrén-Franck
2010-09-16  9:30     ` Joachim Protze
2010-09-16  9:57       ` André Pönitz
2010-09-16  9:49     ` André Pönitz
2010-09-16 11:56       ` Joel Borggrén-Franck
2010-09-16 19:11         ` Tom Tromey [this message]
2010-09-17  7:35           ` Joel Borggrén-Franck
2010-09-21 18:02             ` Tom Tromey
2010-09-16 19:09     ` Tom Tromey

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=m3wrqlpkpd.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=andre.poenitz@nokia.com \
    --cc=gdb@sourceware.org \
    --cc=joel.borggren.franck@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