public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "mlyle at translattice dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/10781] New: Docs missing for some python functionality (cast)
Date: Thu, 15 Oct 2009 07:12:00 -0000	[thread overview]
Message-ID: <20091015071213.10781.mlyle@translattice.com> (raw)

There is no documentation on cast inside the python section (23.2) of the gdb documentation, as seen at 
http://sourceware.org/gdb/current/onlinedocs/gdb_24.html#SEC253 .  I spoke to pmuldoon on IRC who 
thought that perhaps functionality was merged from archer-tromey-python but the doc patchlet was 
forgotten.  

Apologies if this is misfiled, this is my first bug entered on the gdb project.

-- 
           Summary: Docs missing for some python functionality (cast)
           Product: gdb
           Version: 7.0
            Status: UNCONFIRMED
          Severity: minor
          Priority: P2
         Component: python
        AssignedTo: unassigned at sourceware dot org
        ReportedBy: mlyle at translattice dot com
                CC: gdb-prs at sourceware dot org


http://sourceware.org/bugzilla/show_bug.cgi?id=10781

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2009-10-15  7:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-15  7:12 mlyle at translattice dot com [this message]
2009-10-15  7:53 ` [Bug python/10781] " pmuldoon at redhat dot com
2009-10-15  7:56 ` pmuldoon at redhat dot com
2009-10-27 20:51 ` cvs-commit at gcc dot gnu dot org
2009-11-02 17:24 ` pmuldoon at redhat dot com
2009-11-02 17:25 ` pmuldoon at redhat dot com

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=20091015071213.10781.mlyle@translattice.com \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).