This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] 64-bit python support
- From: Ruben Van Boxem <vanboxem dot ruben at gmail dot com>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: gdb-patches at sourceware dot org, mingw64 <mingw-w64-public at lists dot sourceforge dot net>
- Date: Tue, 10 May 2011 16:31:52 +0200
- Subject: Re: [PATCH] 64-bit python support
- References: <BANLkTi=2gphWs2p_5V+wTJMUAkjHDT79uQ__10646.2358417504$1305032253$gmane$org@mail.gmail.com> <m38vuesk7k.fsf@fleche.redhat.com>
- Reply-to: vanboxem dot ruben at gmail dot com
2011/5/10 Tom Tromey <tromey@redhat.com>:
>>>>>> "Ruben" == Ruben Van Boxem <vanboxem.ruben@gmail.com> writes:
>
> Ruben> Attached is a patch that tells gdb-python to use the Py_InitModule4_64
> Ruben> function instead of Py_InitModule for 64-bit builds.
>
> I think this should not be needed. ÂI think the bug must lie somewhere
> else. ÂI say this because Python's modsupport.h should already do this
> renaming:
>
> #if SIZEOF_SIZE_T != SIZEOF_INT
> /* On a 64-bit system, rename the Py_InitModule4 so that 2.4
> Â modules cannot get loaded into a 2.5 interpreter */
> #define Py_InitModule4 Py_InitModule4_64
> #endif
Ah, I didn't know this, that's indeed very handy, but the two
occurrences in my patch are actually still a call to Py_InitModule
without the "4". Then that probably needs to be patched instead?
Ruben
>
> Tom
>