Re: [PATCH v4] Add support for creating new types from the Python API

[Matheus Branco Borella <dark.ryu.550@gmail.com>]

Apologies for my previous empty response, my email client got a little
trigger-happy (And I'm still getting the hang of it).

On Jan 16, 2024, at 9:45=E2=80=AFAM, Eli Zaretskii <eliz@gnu.org> wrote:
> I asked previously what does BIT_SIZE mean for pointer types.  Is it
> the size of the pointer or of the data type to which the pointer
> points?  If it's the size of the pointer, then does it mean this
> function can create pointers of arbitrary sizes regardless of the
> sizes of pointers that are supported by the target?

It's the size of the pointer itself. This feature is mostly intended
for cases where proper types may not be available - such as reverse
engineering - but may still be desirable. While one could get around
the lack of such a function by using `gdb.Type.pointer()`, I felt like
there was no reason to restrict it, and that trusting that the
consumers of the API will pick sizes that are valid for the target was
probably good enough.