public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/17136] 'info type-printers' causes an exception when there are per-objfile printers
Date: Mon, 01 Jun 2015 19:02:00 -0000	[thread overview]
Message-ID: <bug-17136-4717-TncWiyrxIS@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17136-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=17136

dje at google dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dje at google dot com

--- Comment #4 from dje at google dot com ---
Hmmm, I would have expected to see objfile.name, or the correct
objfile.filename, in more places in type_printers.py.
Alas instead of being consistent with pretty-printers,
type-printers have invented a new syntax for the info/enable/disable trio.

All the more reason to put all of this under one piece of common code
used by everyone (pretty-printers, type-printers, xmethods, and so on).
See, e.g., https://sourceware.org/ml/gdb-patches/2015-04/msg00006.html

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2015-06-01 19:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09 12:08 [Bug python/17136] New: " jwakely.gcc at gmail dot com
2014-07-22 18:27 ` [Bug python/17136] " jan.kratochvil at redhat dot com
2014-07-24 17:17 ` keiths at redhat dot com
2015-05-29 12:06 ` jwakely.gcc at gmail dot com
2015-05-29 12:11 ` jwakely.gcc at gmail dot com
2015-06-01 19:02 ` dje at google dot com [this message]
2015-06-01 19:13 ` dje at google dot com
2015-06-01 19:22 ` dje at google dot com
2015-06-26 13:49 ` jan.kratochvil at redhat dot com
2015-08-06 16:26 ` cvs-commit at gcc dot gnu.org
2015-08-06 16:30 ` cvs-commit at gcc dot gnu.org
2015-08-06 16:35 ` dje at google dot com
2023-03-13 13:41 ` cvs-commit at gcc dot gnu.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-17136-4717-TncWiyrxIS@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).