From: Andrew Burgess <aburgess@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>, gdb-patches@sourceware.org
Cc: Andrew Burgess <andrew.burgess@embecosm.com>
Subject: Re: [PATCHv3] gdb/python: add gdb.format_address function
Date: Tue, 22 Mar 2022 13:19:50 +0000 [thread overview]
Message-ID: <87o81yruo9.fsf@redhat.com> (raw)
In-Reply-To: <d384d9c6-d121-3696-a273-3d74bfd42fe3@polymtl.ca>
Simon Marchi via Gdb-patches <gdb-patches@sourceware.org> writes:
>> diff --git a/gdb/python/py-arch.c b/gdb/python/py-arch.c
>> index 0f273b344e4..53906ce506e 100644
>> --- a/gdb/python/py-arch.c
>> +++ b/gdb/python/py-arch.c
>> @@ -62,16 +62,25 @@ arch_object_data_init (struct gdbarch *gdbarch)
>> }
>>
>> /* Returns the struct gdbarch value corresponding to the given Python
>> - architecture object OBJ. */
>> + architecture object OBJ, which must be a gdb.Architecture object. */
>>
>> struct gdbarch *
>> arch_object_to_gdbarch (PyObject *obj)
>> {
>> - arch_object *py_arch = (arch_object *) obj;
>> + gdb_assert (PyObject_TypeCheck (obj, &arch_object_type));
>
> Since we have a function for that, I'd do:
>
> gdb_assert (gdbpy_is_architecture (obj));
>
>> diff --git a/gdb/python/py-progspace.c b/gdb/python/py-progspace.c
>> index 1e01068c59b..f9f2a969e2b 100644
>> --- a/gdb/python/py-progspace.c
>> +++ b/gdb/python/py-progspace.c
>> @@ -504,6 +504,23 @@ pspace_to_pspace_object (struct program_space *pspace)
>> return gdbpy_ref<>::new_reference (result);
>> }
>>
>> +/* See python-internal.h. */
>> +
>> +struct program_space *
>> +progspace_object_to_program_space (PyObject *obj)
>> +{
>> + gdb_assert (PyObject_TypeCheck (obj, &pspace_object_type));
>
> Same here, use gdbpy_is_progspace.
>
> Otherwise, LGTM.
Thanks, I made those changes and pushed this patch.
Andrew
next prev parent reply other threads:[~2022-03-22 13:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 16:17 [PATCH] gdb/python: add gdb.Architecture.format_address Andrew Burgess
2022-02-11 18:54 ` Eli Zaretskii
2022-02-21 17:27 ` Andrew Burgess
2022-02-21 18:02 ` Eli Zaretskii
2022-02-22 13:56 ` Andrew Burgess
2022-02-22 14:48 ` Eli Zaretskii
2022-02-23 14:20 ` Andrew Burgess
2022-03-03 16:49 ` Andrew Burgess
2022-03-03 18:35 ` Craig Blackmore
2022-03-04 10:51 ` Andrew Burgess
2022-03-04 10:50 ` [PATCHv2] " Andrew Burgess
2022-03-04 15:22 ` Simon Marchi
2022-03-07 12:33 ` [PATCHv3] gdb/python: add gdb.format_address function Andrew Burgess
2022-03-21 17:53 ` Andrew Burgess
2022-03-21 18:23 ` Simon Marchi
2022-03-22 13:19 ` Andrew Burgess [this message]
2022-03-23 12:14 ` Simon Marchi
2022-03-23 15:30 ` Andrew Burgess
2022-03-28 21:59 ` Simon Marchi
2022-03-29 13:38 ` Andrew Burgess
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=87o81yruo9.fsf@redhat.com \
--to=aburgess@redhat.com \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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).