From: <Paul.Koning@dell.com>
To: <palves@redhat.com>
Cc: <sergiodj@redhat.com>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH] fix build failure with Python 3.7
Date: Fri, 01 Jun 2018 12:54:00 -0000 [thread overview]
Message-ID: <181F555B-4509-4DA2-9D10-4DF4D47D8E3F@dell.com> (raw)
In-Reply-To: <4e99c685-9047-bb84-8ead-ea13d4c202d3@redhat.com>
> On Jun 1, 2018, at 8:15 AM, Pedro Alves <palves@redhat.com> wrote:
>
> On 05/31/2018 09:45 PM, Paul.Koning@dell.com wrote:
>
>>>> @@ -1667,6 +1667,14 @@ finalize_python (void *ignore)
>>>> restore_active_ext_lang (previous_active);
>>>> }
>>>>
>>>> +#ifdef IS_PY3K
>>>> +PyMODINIT_FUNC
>>>> +PyInit__gdb (void)
>>>> +{
>>>> + return PyModule_Create (&python_GdbModuleDef);
>>>> +}
>>>> +#endif
>>>
>>> I think it's a good idea to add a comment to this function.
>>
>> I added this (after the #ifdef):
>>
>> /* This is called via the PyImport_AppendInittab mechanism called
>> during initialization, to make the built-in _gdb module known to
>> Python. */
>
> Can the function be made static?
No; I did that first but PyMODINIT_FUNC is a #define that conflicts with "static".
> I'm a little surprised to see the function being named "Py...", since
> that kind of looks like stepping in Python's namespace.
True. How about "init__gdb_module"?
paul
next prev parent reply other threads:[~2018-06-01 12:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 18:20 Paul.Koning
2018-05-31 20:45 ` Sergio Durigan Junior
2018-05-31 21:25 ` Paul.Koning
2018-06-01 1:27 ` Tom Tromey
2018-06-01 11:58 ` Phil Muldoon
[not found] ` <87d0xb34jw.fsf@redhat.com>
2018-06-01 11:56 ` Phil Muldoon
2018-06-01 12:16 ` Pedro Alves
2018-06-01 12:54 ` Paul.Koning [this message]
2018-06-01 13:10 ` Pedro Alves
2018-06-01 13:22 ` Paul.Koning
2018-06-01 13:36 ` Pedro Alves
2018-06-01 13:37 ` Pedro Alves
2018-06-01 13:47 ` Paul.Koning
2018-06-08 14:35 ` Pedro Alves
2018-06-08 14:37 ` Paul.Koning
2018-06-08 14:55 ` Pedro Alves
2018-06-08 17:36 ` Paul.Koning
2018-06-09 0:26 ` Sergio Durigan Junior
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=181F555B-4509-4DA2-9D10-4DF4D47D8E3F@dell.com \
--to=paul.koning@dell.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=sergiodj@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).