From: Chris Moller <cmoller@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: pr9164 patch
Date: Tue, 09 Feb 2010 01:23:00 -0000 [thread overview]
Message-ID: <4B70B90F.7060409@redhat.com> (raw)
In-Reply-To: <20100208233407.GA30829@caradoc.them.org>
On 02/08/10 18:34, Daniel Jacobowitz wrote:
> On Mon, Feb 08, 2010 at 06:17:46PM -0500, Chris Moller wrote:
>
>> I was rooting around in the gdb c++ bug list a bit ago and came
>> across this one: "sizeof should have unsigned type in print
>> expressions." Assuming that, as in C/C++, size_t is typedeffed from
>> unsigned int, the fix is a one-line patch in c-exp.y, attached. If
>> that assumption is wrong, well, never mind...
>>
>
> Try it on x86_64 - size_t is platform dependent, and it's often
> unsigned long.
>
I did--it's 4 bytes on both i386 and x86_64. I just don't know about
non-intel archs.
next prev parent reply other threads:[~2010-02-09 1:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 23:17 Chris Moller
2010-02-08 23:34 ` Daniel Jacobowitz
2010-02-09 1:23 ` Chris Moller [this message]
2010-02-09 2:18 ` Daniel Jacobowitz
2010-02-09 2:38 ` Chris Moller
2010-02-08 23:38 ` Pedro Alves
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=4B70B90F.7060409@redhat.com \
--to=cmoller@redhat.com \
--cc=gdb-patches@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