public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Roland Schwingel <roland@onevision.com>
To: insight@sourceware.org, Keith Seitz <keiths@redhat.com>,
	       Patrick.Monnerat@datasphere.ch
Subject: Re: [PATCH] print format does not match argument type
Date: Tue, 10 Apr 2012 16:59:00 -0000	[thread overview]
Message-ID: <4F8466B3.8040805@onevision.com> (raw)

Hi...

Keith Seitz <keiths@redhat.com> wrote on 10.04.2012 18:27:42:

 > On 04/10/2012 09:08 AM, Patrick Monnerat wrote:
 > > I think I've found the universal (well: almost!) coding:
 > >
 > > Use format "%llx" and cast arg to (unsigned long long): This is
 > > C99 and supported by MSVC, at least since 2005. Not OK for C89 :-(
MS is not really caring about standards ... for native printf on windows 
(as deliverd in msvcrt.dll) "%llx" is not supported.

 > But for now, if your suggestion works (Roland will hopefully verify),
 > then I say we go with that for the time being.
I am already testing but seeing a "funny" hang now when opening
the register window when using %llx.

Still evaluating. Have to see what xstrprintf() does exactly.
But as far as I can see at the moment it appears that vasprintf is 
getting handled by libiberty in gdb on windows.

Roland

BTW: Insight is not built using MSVC on windows, but with gcc...

             reply	other threads:[~2012-04-10 16:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-10 16:59 Roland Schwingel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-04-11 11:38 Roland Schwingel
2012-04-11 17:24 ` Patrick Monnerat
2012-04-10 14:30 Roland Schwingel
2012-04-10 15:10 ` Patrick Monnerat
2012-04-10 16:08 ` Patrick Monnerat
2012-04-10 16:28   ` Keith Seitz
2012-04-13 14:52     ` Pierre Muller
2012-04-13 15:18       ` Keith Seitz
2012-04-13 15:25         ` Pierre Muller
2012-04-05 16:34 Patrick Monnerat

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=4F8466B3.8040805@onevision.com \
    --to=roland@onevision.com \
    --cc=Patrick.Monnerat@datasphere.ch \
    --cc=insight@sourceware.org \
    --cc=keiths@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).