From: Mike Frysinger <vapier@gentoo.org>
To: Ozkan Sezer <sezeroz@gmail.com>
Cc: gdb-patches@sourceware.org, Tom Tromey <tromey@redhat.com>
Subject: Re: [PATCH] [Windows] fix format string for 64 bit var in gdbserver
Date: Sat, 17 Jul 2010 18:50:00 -0000 [thread overview]
Message-ID: <201007171447.38746.vapier@gentoo.org> (raw)
In-Reply-To: <AANLkTilx-ZW3cEZEbBn__kZDTHxk3IWEBPFoooGtRBy_@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1810 bytes --]
On Saturday, July 17, 2010 05:53:04 Ozkan Sezer wrote:
> On Sat, Jul 17, 2010 at 12:42 PM, Ozkan Sezer <sezeroz@gmail.com> wrote:
> > On Sat, Jul 17, 2010 at 12:37 PM, Mike Frysinger <vapier@gentoo.org>
wrote:
> >> On Friday, July 16, 2010 16:10:23 Ozkan Sezer wrote:
> >>> For windows targets, (x86_64-w64-mingw32, i686-w64-mingw32)
> >>> gcc complains:
> >>>
> >>> ../../../gdb-cvs/gdb/gdbserver/server.c: In function 'handle_query':
> >>> ../../../gdb-cvs/gdb/gdbserver/server.c:1542: warning: unknown
> >>> conversion type character 'l' in format
> >>> ../../../gdb-cvs/gdb/gdbserver/server.c:1542: warning: too many
> >>> arguments for format
> >>> ../../../gdb-cvs/gdb/gdbserver/server.c:1566: warning: unknown
> >>> conversion type character 'l' in format
> >>> ../../../gdb-cvs/gdb/gdbserver/server.c:1566: warning: too many
> >>> arguments for format
> >>>
> >>> This is due to the fact that MS printf doesn't support %lld, it uses
> >>> its own %I64d which gcc already knows about. The attached patch
> >>> changes that. OK for apply?
> >>
> >> ugh, no. why not use a sane define like PRIx64 from inttypes.h ?
> >
> > I would happily do that, however that would require inttypes
> > module merge from gnulib to gdb/gnulib, am I wrong?
>
> To be clear, I modified a patch I submitted before to not use
> the inttypes PRI macros:
> http://sourceware.org/ml/gdb-patches/2010-07/msg00244.html
>
> By analogy, I might use paddress() instead, but for that case
> please see the issue I reported at
> http://sourceware.org/ml/gdb-patches/2010-07/msg00254.html
>
> Comments?
random #ifdefs like this are highly discouraged. if you could find another
way, that'd be great. but i dont think importing a few small modules from
gnulib is a big deal ?
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2010-07-17 18:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 20:10 Ozkan Sezer
2010-07-17 9:40 ` Mike Frysinger
2010-07-17 9:42 ` Ozkan Sezer
2010-07-17 9:53 ` Ozkan Sezer
2010-07-17 18:50 ` Mike Frysinger [this message]
2010-07-17 18:59 ` Ozkan Sezer
2010-07-17 19:19 ` Mike Frysinger
2010-07-17 19:23 ` Ozkan Sezer
2010-07-17 21:01 ` Andreas Schwab
2010-07-17 21:05 ` Ozkan Sezer
2010-07-20 18:20 ` Ozkan Sezer
2010-07-17 12:29 ` Mark Kettenis
2010-07-17 18:49 ` Mike Frysinger
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=201007171447.38746.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gdb-patches@sourceware.org \
--cc=sezeroz@gmail.com \
--cc=tromey@redhat.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