public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "markflorisson88 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/12175] New: show_doc for gdb.Parameter has strange behaviour
Date: Sun, 31 Oct 2010 20:53:00 -0000 [thread overview]
Message-ID: <bug-12175-4717@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=12175
Summary: show_doc for gdb.Parameter has strange behaviour
Product: gdb
Version: 7.1
Status: NEW
Severity: normal
Priority: P2
Component: python
AssignedTo: unassigned@sourceware.org
ReportedBy: markflorisson88@gmail.com
The show doc is not shown properly. In the next example the show_doc is totally
different from the output that's actually shown. Not only does it drop
everything after the '.', it also manages to translate 'This' to 'Is'.
(gdb) python
>class Param(gdb.Parameter):
> show_doc = "This is the show doc. This part is not shown!"
>
>Param("some-param", gdb.COMMAND_NONE, gdb.PARAM_BOOLEAN)
>end
(gdb) show some-param
Is the show doc is off.
--
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.
next reply other threads:[~2010-10-31 20:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-31 20:53 markflorisson88 at gmail dot com [this message]
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
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@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).