From: Andrew STUBBS <andrew.stubbs@st.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] long long for printf on MinGW
Date: Mon, 16 Oct 2006 09:45:00 -0000 [thread overview]
Message-ID: <453354A0.4070906@st.com> (raw)
In-Reply-To: <200610151745.k9FHjvPa017960@elgar.sibelius.xs4all.nl>
Mark Kettenis wrote:
> I'm not sure it "ought to work". The host printf(3) doesn't support
> "%lld", so why should gdb support it?
How about 'because it can'?
> If your answer is "because the target printf(3) supports it", then
> think again. By using the host printf(3) like we now do, the gdb
> printf prints types with widths as they are on the host, and not as
> they are on the target.
I'm rather more interested in the usability of the debugger than
niceties of implementation.
When a customer reports that a feature doesn't work on a platform, I
don't like to tell them that it shouldn't work unless I have a really
good reason. If Windows only had a 62 bit printf (or something else
ridiculous) then that might qualify, but I can't find a reason in this case.
Andrew
prev parent reply other threads:[~2006-10-16 9:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 11:21 Andrew STUBBS
2006-10-11 13:03 ` Daniel Jacobowitz
2006-10-11 15:12 ` Andrew STUBBS
2008-04-22 19:41 ` Daniel Jacobowitz
2008-04-23 10:26 ` Andrew STUBBS
2008-04-23 12:18 ` Daniel Jacobowitz
2008-04-23 16:12 ` Andrew STUBBS
2006-10-11 20:28 ` Mark Kettenis
2006-10-11 20:44 ` Daniel Jacobowitz
2006-10-12 10:09 ` Andrew STUBBS
[not found] ` <200610151745.k9FHjvPa017960@elgar.sibelius.xs4all.nl>
2006-10-16 9:45 ` Andrew STUBBS [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=453354A0.4070906@st.com \
--to=andrew.stubbs@st.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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