public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "pmuldoon at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/12175] show_doc for gdb.Parameter has strange behaviour
Date: Tue, 16 Nov 2010 15:30:00 -0000	[thread overview]
Message-ID: <bug-12175-4717-tLe7FlgJEE@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12175-4717@http.sourceware.org/bugzilla/>

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

--- Comment #4 from Phil Muldoon <pmuldoon at redhat dot com> 2010-11-16 15:14:09 UTC ---
Yeah, we can.  First we would have to identify the parameter as being written
in Python.  Then we would require the user to implement show/set documentation
functions in Python.  Then, when the value printing/help parameter code
sections are executed in GDB we can check if it is a Python scripted parameter,
and if so then call into the Python object where it would return the
appropriate string for the above functions.

This would be an API regression on our part though. We might be able to do this
generically which would avoid requiring parameter API changes, but not sure
how.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2010-11-16 15:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-31 20:53 [Bug python/12175] New: " markflorisson88 at gmail dot com
2010-10-31 20:53 ` [Bug python/12175] " markflorisson88 at gmail dot com
2010-11-16 12:15 ` pmuldoon at redhat dot com
2010-11-16 12:16 ` pmuldoon at redhat dot com
2010-11-16 14:35 ` pmuldoon at redhat dot com
2010-11-16 15:14 ` pedro at codesourcery dot com
2010-11-16 15:30 ` pmuldoon at redhat dot com [this message]
2010-11-16 16:29 ` pedro at codesourcery dot com
2011-03-14 17:57 ` pmuldoon at redhat dot com
2011-03-16 10:29 ` 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=bug-12175-4717-tLe7FlgJEE@http.sourceware.org/bugzilla/ \
    --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).