Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: GDB printf command
Date: Wed, 18 Oct 2006 13:53:00 -0000	[thread overview]
Message-ID: <20061018135305.GA7083@nevyn.them.org> (raw)
In-Reply-To: <45360ECE.4060506@st.com>

On Wed, Oct 18, 2006 at 12:23:58PM +0100, Andrew STUBBS wrote:
> Daniel Jacobowitz wrote:
> >Once we have the structure in place, we could basically replace
> >printf_fetchargs (which uses va_arg) with something that operated on
> >our list of values and did appropriate type checking / casts, then
> >hand it back to the gnulib printf routine.
> 
> So you're not talking about changing anything outside of printcmd.c, 
> just adding a few files from another project and rewriting the relevant 
> bits of the printf command?

Right.  Our value infrastructure is more than adequate for what we
need.  We'll end up with more total code, but less of our own; gnulib
will do most of the heavy lifting.

> OK, that sounds like a plan. Where do we start?

Well, the very first thing is going to be a version of gnulib that lets
us reuse its printf this way.  I'll contact the gnulib maintainers
about that right now, and get back to you.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-10-18 13:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-17 12:03 Andrew STUBBS
2006-10-17 13:24 ` Daniel Jacobowitz
2006-10-17 14:10   ` Andrew STUBBS
2006-10-17 14:25     ` Daniel Jacobowitz
2006-10-17 14:43       ` Andrew STUBBS
2006-10-17 14:54         ` Daniel Jacobowitz
2006-10-18 11:24           ` Andrew STUBBS
2006-10-18 13:53             ` Daniel Jacobowitz [this message]
2006-10-31 11:43             ` Andrew STUBBS
2006-10-31 13:42               ` Daniel Jacobowitz

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=20061018135305.GA7083@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@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