From: Luis via Gdb <gdb@sourceware.org>
To: Vacha Bhavsar <vacha.bhavsar@oss.qualcomm.com>
Cc: gdb@sourceware.org
Subject: Re: Question Regarding Int Cast Error in GDB Python
Date: Tue, 26 Aug 2025 21:49:48 +0100 [thread overview]
Message-ID: <21e45c38-4240-4238-abcf-027ca05a36a1@gmail.com> (raw)
In-Reply-To: <CAEWVDmt87GgX6xyBzYLkzHME_ja7G1daTbD1jOWgHNBRygPpLw@mail.gmail.com>
Hi,
On 8/25/25 14:29, Vacha Bhavsar wrote:
> Hi,
>
> Apologies, it seems I pasted the wrong snippet in the original email.
> The code in my reply just prior to this is the correct code. The snippet
> that
> should have been included in the first email, which causes the error, is
> the one below:
>
> v = gdb.parse_and_eval(reg)
> report(str(v.type) == "uint128_t", "size of %s" % (reg))
Right, so gdb doesn't like casting integers to/from 8+ bytes. That's a
limitation currently. But why are you considering this particular cast?
To optimize the checks instead of using the byte vectors?
next prev parent reply other threads:[~2025-08-26 20:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 18:21 Vacha Bhavsar via Gdb
2025-08-25 8:35 ` Luis via Gdb
2025-08-25 13:23 ` Vacha Bhavsar via Gdb
2025-08-25 13:29 ` Vacha Bhavsar via Gdb
2025-08-26 20:49 ` Luis via Gdb [this message]
2025-08-27 19:16 ` Vacha Bhavsar via Gdb
2025-08-29 17:46 ` Tom Tromey
2025-09-03 18:59 ` Vacha Bhavsar via Gdb
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=21e45c38-4240-4238-abcf-027ca05a36a1@gmail.com \
--to=gdb@sourceware.org \
--cc=luis.machado.foss@gmail.com \
--cc=vacha.bhavsar@oss.qualcomm.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