From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: GDB printf command
Date: Tue, 31 Oct 2006 13:42:00 -0000 [thread overview]
Message-ID: <20061031134244.GA17937@nevyn.them.org> (raw)
In-Reply-To: <454736EB.9050206@st.com>
On Tue, Oct 31, 2006 at 11:43:39AM +0000, Andrew STUBBS wrote:
> >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.
>
> From what I can see in the bug-gnulib archives, this seems to have hit
> a problem.
>
> What's going on?
I didn't get an answer to one of my questions. I meant to come up with
a patch to suggest, to restart the discussion, but you know how things
are - I haven't had time.
I will be back to it eventually; I'm afraid that's all I can promise
:-( Maybe this week.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-10-31 13:42 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
2006-10-31 11:43 ` Andrew STUBBS
2006-10-31 13:42 ` Daniel Jacobowitz [this message]
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=20061031134244.GA17937@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