This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Fix gdb.Value->python conversion for large unsigned ints
- From: Doug Evans <dje at google dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: gdb-patches <gdb-patches at sourceware dot org>
- Date: Thu, 6 Oct 2016 10:50:51 -0700
- Subject: Re: [PATCH] Fix gdb.Value->python conversion for large unsigned ints
- Authentication-results: sourceware.org; auth=none
- References: <001a114592c831ba11052f3ea8b0@google.com> <95309e87-7b97-7c8f-9b78-cc2082eef537@redhat.com>
[sorry for the resend ...
We've got gdb to use c++ now. Yay.
Can we maybe someday get the list to not bounce text/html?]
On Tue, Oct 4, 2016 at 7:40 AM, Pedro Alves <palves@redhat.com> wrote:
> Hi Doug,
>
> On 03/30/2016 07:57 AM, Doug Evans wrote:
>> Hi.
>>
>> I was seeing this in gdb:
>>
>> (gdb) py print long(gdb.Value(18446744071563607160))
>> -2145944456
>>
>> whereas with plain python:
>>
>> (gdb) py print long(18446744071563607160)
>> 18446744071563607160
>>
>
> Looks like this fell through the cracks?
>
> LGTM.
>
>> 2016-03-29 Doug Evans <dje@google.com>
>>
>> * python/py-value.c (valpy_long): Handle unsigned values.
>>
>> testsuite/
>> * gdb.python/py-value.exp (test_value_creation): Add test for large
>> unsigned 64-bit value.
>
> Thanks,
> Pedro Alves
>
Thanks!
I usually do an audit of email sent to gdb-patches every few months.
Totally missed this one (and potentially others - a distracting year
for many reasons -
I'll go through and try to find if there's any more).
Committed.