Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Doug Evans <dje@google.com>
Cc: Paul Pluzhnikov <ppluzhnikov@google.com>,
		Vladimir Prus <vladimir@codesourcery.com>,
	tromey@redhat.com, 	gdb@sources.redhat.com
Subject: Re: Registering pretty-printers
Date: Fri, 12 Jun 2009 16:51:00 -0000	[thread overview]
Message-ID: <20090612165133.GA12951@caradoc.them.org> (raw)
In-Reply-To: <e394668d0906120943q5bcc9a92xe94b9ba199d2ffe8@mail.gmail.com>

On Fri, Jun 12, 2009 at 12:43:12PM -0400, Doug Evans wrote:
> On Thu, Jun 11, 2009 at 8:51 PM, Daniel Jacobowitz<drow@false.org> wrote:
> > In my opinion, anything that increases the size of the executable is a
> > non-starter.  I don't think there's any reliable way to create a
> > non-allocatable section, and it would have other problems, like
> > duplicate elimination.
> 
> Reliable in what sense?  [I realize the term is pretty unambiguous.
> I'm guessing I'm missing something as it doesn't seem to be
> excessively hard for many important targets.]  Or did you mean
> portable?

Poor choice of word.  Same thing Vladimir was talking about, though,
in essence.  I don't want the only decent solution to be one that
requires pushing new tools out.  Fedora can do that; maybe Google can
too, I don't know anything about your development environments.  But
plenty of other places can't.

I think Vladimir's got a solid point - we need a way to just point the
debugger at files and have them go.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2009-06-12 16:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-07 23:11 Vladimir Prus
2009-06-10 19:25 ` Tom Tromey
2009-06-11  8:29   ` Vladimir Prus
2009-06-11 17:14     ` Paul Pluzhnikov
2009-06-12  0:52       ` Daniel Jacobowitz
2009-06-12  7:20         ` Vladimir Prus
2009-06-12 16:43         ` Doug Evans
2009-06-12 16:51           ` Daniel Jacobowitz [this message]
2009-06-12 17:12             ` Doug Evans
2009-06-12 17:06         ` Tom Tromey
2009-06-12 17:36     ` Tom Tromey
2009-06-12 17:43       ` Vladimir Prus
2009-06-15 20:23         ` Tom Tromey
2009-06-26 20:37           ` Tom Tromey
2009-06-27 10:16             ` Vladimir Prus

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=20090612165133.GA12951@caradoc.them.org \
    --to=drow@false.org \
    --cc=dje@google.com \
    --cc=gdb@sources.redhat.com \
    --cc=ppluzhnikov@google.com \
    --cc=tromey@redhat.com \
    --cc=vladimir@codesourcery.com \
    /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