public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug python/14513] setting extended-prompt triggers spurious newline to be emitted Date: Mon, 04 May 2015 17:05:00 -0000 [thread overview] Message-ID: <bug-14513-4717-FIBg4oxiWT@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-14513-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=14513 Tom Tromey <tromey at sourceware dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot org --- Comment #2 from Tom Tromey <tromey at sourceware dot org> --- The discussion in late 2013 seems to have petered out. I've been using this locally: diff --git a/gdb/python/py-param.c b/gdb/python/py-param.c index 06b9ae9..b395f9d 100644 --- a/gdb/python/py-param.c +++ b/gdb/python/py-param.c @@ -387,8 +387,12 @@ get_set_value (char *args, int from_tty, set_doc_string = get_doc_string (obj, set_doc_cst); } +#if 0 + /* See https://sourceware.org/bugzilla/show_bug.cgi?id=14513. + There's no reason to print anything here. */ make_cleanup (xfree, set_doc_string); fprintf_filtered (gdb_stdout, "%s\n", set_doc_string); +#endif Py_XDECREF (set_doc_func); do_cleanups (cleanup); -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2015-05-04 17:05 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-23 18:32 [Bug python/14513] New: " vapier at gentoo dot org 2012-08-24 18:20 ` [Bug python/14513] " tromey at redhat dot com 2013-09-18 13:18 ` pmuldoon at redhat dot com 2015-03-14 15:58 ` seb93250 at gmail dot com 2015-05-04 17:05 ` tromey at sourceware dot org [this message] 2015-05-04 19:45 ` tromey at sourceware dot org
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-14513-4717-FIBg4oxiWT@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: linkBe 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).