Segfault when building wxPython with SIP 4.19.11

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

Segfault when building wxPython with SIP 4.19.11

Scott Talbert
Hi,

I'm seeing a segfault when building wxPython with SIP 4.19.11.

Running command: sip
/usr/bin/sip -w -o -g -I /home/talbert/Downloads/wxPython-4.0.1/src -I
/home/talbert/Downloads/wxPython-4.0.1/sip/gen -c /tmp/tmpdH4lfu -b
sip/cpp/_core.sbf -X pycode_core:wx/core.py sip/gen/_core.sip
Segmentation fault (core dumped)

(gdb) bt
#0  prcode (fp=fp@entry=0x55f0f0d13ed0, fmt=0x55f0f042adc7
"\");\n#else\n",
     fmt@entry=0x55f0f042ad58 "    /* Get the SIP module's API. */\n#if
PY_VERSION_HEX >= 0x02050000\n    sip_sipmod =
PyImport_ImportModule(\"%s\");\n#else\n")
     at ./sipgen/gencode.c:14489
#1  0x000055f0f04004e6 in generateSipImport (mod=0x55f0f0d14180,
     fp=0x55f0f0d13ed0, sipName=0x0) at ./sipgen/gencode.c:2775
#2  generateCpp (pt=pt@entry=0x7ffd5c4cabc0, mod=<optimized out>,
     codeDir=codeDir@entry=0x7ffd5c4cc455 "/tmp/tmpdH4lfu",
     srcSuffix=srcSuffix@entry=0x55f0f0422866 ".cpp", parts=parts@entry=0,
     needed_qualifiers=needed_qualifiers@entry=0x0, xsl=0x0, py_debug=0,
     sipName=0x0) at ./sipgen/gencode.c:2561
#3  0x000055f0f0403269 in generateCode (pt=0x7ffd5c4cabc0,
     codeDir=0x7ffd5c4cc455 "/tmp/tmpdH4lfu",
     buildFile=0x7ffd5c4cc467 "sip/cpp/_core.sbf", docFile=<optimized out>,
     srcSuffix=0x55f0f0422866 ".cpp", except=<optimized out>, trace=0,
     releaseGIL=1, parts=0, needed_qualifiers=0x0, xsl=0x0, consModule=0x0,
     docs=1, py_debug=0, sipName=0x0) at ./sipgen/gencode.c:358
#4  0x000055f0f03e4e15 in main (argc=15, argv=0x7ffd5c4cae58)
     at ./sipgen/main.c:291

4.19.8 worked ok.

Thanks,
Scott
_______________________________________________
PyQt mailing list    [hidden email]
https://www.riverbankcomputing.com/mailman/listinfo/pyqt
Reply | Threaded
Open this post in threaded view
|

Re: Segfault when building wxPython with SIP 4.19.11

Phil Thompson-5
On 06/07/2018 05:10, Scott Talbert wrote:

> Hi,
>
> I'm seeing a segfault when building wxPython with SIP 4.19.11.
>
> Running command: sip
> /usr/bin/sip -w -o -g -I /home/talbert/Downloads/wxPython-4.0.1/src -I
> /home/talbert/Downloads/wxPython-4.0.1/sip/gen -c /tmp/tmpdH4lfu -b
> sip/cpp/_core.sbf -X pycode_core:wx/core.py sip/gen/_core.sip
> Segmentation fault (core dumped)
>
> (gdb) bt
> #0  prcode (fp=fp@entry=0x55f0f0d13ed0, fmt=0x55f0f042adc7
> "\");\n#else\n",
>     fmt@entry=0x55f0f042ad58 "    /* Get the SIP module's API. */\n#if
> PY_VERSION_HEX >= 0x02050000\n    sip_sipmod =
> PyImport_ImportModule(\"%s\");\n#else\n")
>     at ./sipgen/gencode.c:14489
> #1  0x000055f0f04004e6 in generateSipImport (mod=0x55f0f0d14180,
>     fp=0x55f0f0d13ed0, sipName=0x0) at ./sipgen/gencode.c:2775
> #2  generateCpp (pt=pt@entry=0x7ffd5c4cabc0, mod=<optimized out>,
>     codeDir=codeDir@entry=0x7ffd5c4cc455 "/tmp/tmpdH4lfu",
>     srcSuffix=srcSuffix@entry=0x55f0f0422866 ".cpp",
> parts=parts@entry=0,
>     needed_qualifiers=needed_qualifiers@entry=0x0, xsl=0x0, py_debug=0,
>     sipName=0x0) at ./sipgen/gencode.c:2561
> #3  0x000055f0f0403269 in generateCode (pt=0x7ffd5c4cabc0,
>     codeDir=0x7ffd5c4cc455 "/tmp/tmpdH4lfu",
>     buildFile=0x7ffd5c4cc467 "sip/cpp/_core.sbf", docFile=<optimized
> out>,
>     srcSuffix=0x55f0f0422866 ".cpp", except=<optimized out>, trace=0,
>     releaseGIL=1, parts=0, needed_qualifiers=0x0, xsl=0x0,
> consModule=0x0,
>     docs=1, py_debug=0, sipName=0x0) at ./sipgen/gencode.c:358
> #4  0x000055f0f03e4e15 in main (argc=15, argv=0x7ffd5c4cae58)
>     at ./sipgen/main.c:291
>
> 4.19.8 worked ok.

It should be fixed in the current snapshot. 4.19.12 will be released
over the weekend.

Phil

_______________________________________________
PyQt mailing list    [hidden email]
https://www.riverbankcomputing.com/mailman/listinfo/pyqt
Reply | Threaded
Open this post in threaded view
|

Re: Segfault when building wxPython with SIP 4.19.11

Phil Thompson-5
On 06/07/2018 08:47, Phil Thompson wrote:

> On 06/07/2018 05:10, Scott Talbert wrote:
>> Hi,
>>
>> I'm seeing a segfault when building wxPython with SIP 4.19.11.
>>
>> Running command: sip
>> /usr/bin/sip -w -o -g -I /home/talbert/Downloads/wxPython-4.0.1/src -I
>> /home/talbert/Downloads/wxPython-4.0.1/sip/gen -c /tmp/tmpdH4lfu -b
>> sip/cpp/_core.sbf -X pycode_core:wx/core.py sip/gen/_core.sip
>> Segmentation fault (core dumped)
>>
>> (gdb) bt
>> #0  prcode (fp=fp@entry=0x55f0f0d13ed0, fmt=0x55f0f042adc7
>> "\");\n#else\n",
>>     fmt@entry=0x55f0f042ad58 "    /* Get the SIP module's API. */\n#if
>> PY_VERSION_HEX >= 0x02050000\n    sip_sipmod =
>> PyImport_ImportModule(\"%s\");\n#else\n")
>>     at ./sipgen/gencode.c:14489
>> #1  0x000055f0f04004e6 in generateSipImport (mod=0x55f0f0d14180,
>>     fp=0x55f0f0d13ed0, sipName=0x0) at ./sipgen/gencode.c:2775
>> #2  generateCpp (pt=pt@entry=0x7ffd5c4cabc0, mod=<optimized out>,
>>     codeDir=codeDir@entry=0x7ffd5c4cc455 "/tmp/tmpdH4lfu",
>>     srcSuffix=srcSuffix@entry=0x55f0f0422866 ".cpp",
>> parts=parts@entry=0,
>>     needed_qualifiers=needed_qualifiers@entry=0x0, xsl=0x0,
>> py_debug=0,
>>     sipName=0x0) at ./sipgen/gencode.c:2561
>> #3  0x000055f0f0403269 in generateCode (pt=0x7ffd5c4cabc0,
>>     codeDir=0x7ffd5c4cc455 "/tmp/tmpdH4lfu",
>>     buildFile=0x7ffd5c4cc467 "sip/cpp/_core.sbf", docFile=<optimized
>> out>,
>>     srcSuffix=0x55f0f0422866 ".cpp", except=<optimized out>, trace=0,
>>     releaseGIL=1, parts=0, needed_qualifiers=0x0, xsl=0x0,
>> consModule=0x0,
>>     docs=1, py_debug=0, sipName=0x0) at ./sipgen/gencode.c:358
>> #4  0x000055f0f03e4e15 in main (argc=15, argv=0x7ffd5c4cae58)
>>     at ./sipgen/main.c:291
>>
>> 4.19.8 worked ok.
>
> It should be fixed in the current snapshot. 4.19.12 will be released
> over the weekend.

However there are slight changes to the way a private sip module is
specified. I don’t know if this affects how wxPython is built.

Phil

_______________________________________________
PyQt mailing list    [hidden email]
https://www.riverbankcomputing.com/mailman/listinfo/pyqt
Reply | Threaded
Open this post in threaded view
|

Re: Segfault when building wxPython with SIP 4.19.11

Scott Talbert
On Fri, 6 Jul 2018, Phil Thompson wrote:

>>> Hi,
>>>
>>> I'm seeing a segfault when building wxPython with SIP 4.19.11.
>>>
>>> Running command: sip
>>> /usr/bin/sip -w -o -g -I /home/talbert/Downloads/wxPython-4.0.1/src -I
>>> /home/talbert/Downloads/wxPython-4.0.1/sip/gen -c /tmp/tmpdH4lfu -b
>>> sip/cpp/_core.sbf -X pycode_core:wx/core.py sip/gen/_core.sip
>>> Segmentation fault (core dumped)
>>>
>>> (gdb) bt
>>> #0  prcode (fp=fp@entry=0x55f0f0d13ed0, fmt=0x55f0f042adc7
>>> "\");\n#else\n",
>>>     fmt@entry=0x55f0f042ad58 "    /* Get the SIP module's API. */\n#if
>>> PY_VERSION_HEX >= 0x02050000\n    sip_sipmod =
>>> PyImport_ImportModule(\"%s\");\n#else\n")
>>>     at ./sipgen/gencode.c:14489
>>> #1  0x000055f0f04004e6 in generateSipImport (mod=0x55f0f0d14180,
>>>     fp=0x55f0f0d13ed0, sipName=0x0) at ./sipgen/gencode.c:2775
>>> #2  generateCpp (pt=pt@entry=0x7ffd5c4cabc0, mod=<optimized out>,
>>>     codeDir=codeDir@entry=0x7ffd5c4cc455 "/tmp/tmpdH4lfu",
>>>     srcSuffix=srcSuffix@entry=0x55f0f0422866 ".cpp", parts=parts@entry=0,
>>>     needed_qualifiers=needed_qualifiers@entry=0x0, xsl=0x0, py_debug=0,
>>>     sipName=0x0) at ./sipgen/gencode.c:2561
>>> #3  0x000055f0f0403269 in generateCode (pt=0x7ffd5c4cabc0,
>>>     codeDir=0x7ffd5c4cc455 "/tmp/tmpdH4lfu",
>>>     buildFile=0x7ffd5c4cc467 "sip/cpp/_core.sbf", docFile=<optimized out>,
>>>     srcSuffix=0x55f0f0422866 ".cpp", except=<optimized out>, trace=0,
>>>     releaseGIL=1, parts=0, needed_qualifiers=0x0, xsl=0x0, consModule=0x0,
>>>     docs=1, py_debug=0, sipName=0x0) at ./sipgen/gencode.c:358
>>> #4  0x000055f0f03e4e15 in main (argc=15, argv=0x7ffd5c4cae58)
>>>     at ./sipgen/main.c:291
>>>
>>> 4.19.8 worked ok.
>>
>> It should be fixed in the current snapshot. 4.19.12 will be released
>> over the weekend.
>
> However there are slight changes to the way a private sip module is
> specified. I don’t know if this affects how wxPython is built.
I don't know either.  When I build wxPython, I am building it for Fedora
or Debian packages, and I build it using the public sip module, stripping
out the bundled copy.

Scott
_______________________________________________
PyQt mailing list    [hidden email]
https://www.riverbankcomputing.com/mailman/listinfo/pyqt
Reply | Threaded
Open this post in threaded view
|

Re: Segfault when building wxPython with SIP 4.19.11

Hans-Peter Jansen-2
On Freitag, 6. Juli 2018 09:32:14 Scott Talbert wrote:

> On Fri, 6 Jul 2018, Phil Thompson wrote:
>
> >>> 4.19.8 worked ok.
> >>
> >> It should be fixed in the current snapshot. 4.19.12 will be released
> >> over the weekend.
> >
> > However there are slight changes to the way a private sip module is
> > specified. I don’t know if this affects how wxPython is built.
>
> I don't know either.  When I build wxPython, I am building it for Fedora
> or Debian packages, and I build it using the public sip module, stripping
> out the bundled copy.

Well, I guess, the idea behind bundling sip is to allow local adjustments
without compromising the public sip package and other dependent projects.

>From packaging point of view, you should take the "other" route.. I'm facing
the same issue for openSUSE, but will wait a little longer to let things
settle...

Cheers,
Pete

_______________________________________________
PyQt mailing list    [hidden email]
https://www.riverbankcomputing.com/mailman/listinfo/pyqt
Reply | Threaded
Open this post in threaded view
|

Re: Segfault when building wxPython with SIP 4.19.11

Scott Talbert
On Fri, 6 Jul 2018, Hans-Peter Jansen wrote:

>> >>> 4.19.8 worked ok.
>> >>
>> >> It should be fixed in the current snapshot. 4.19.12 will be released
>> >> over the weekend.
>> >
>> > However there are slight changes to the way a private sip module is
>> > specified. I don’t know if this affects how wxPython is built.
>>
>> I don't know either.  When I build wxPython, I am building it for Fedora
>> or Debian packages, and I build it using the public sip module, stripping
>> out the bundled copy.
>
> Well, I guess, the idea behind bundling sip is to allow local adjustments
> without compromising the public sip package and other dependent projects.
>
>> From packaging point of view, you should take the "other" route.. I'm facing
> the same issue for openSUSE, but will wait a little longer to let things
> settle...
Well, in the case of wxPython, the primary reason for unbundling is that
the default build process downloads a precompiled SIP binary from the
wxPython website.  That's problematic for most distributions.  :)

I don't think that wxPython makes any local adjustments to its bundled
copy of SIP, at least that I've noticed.

Scott
_______________________________________________
PyQt mailing list    [hidden email]
https://www.riverbankcomputing.com/mailman/listinfo/pyqt
Reply | Threaded
Open this post in threaded view
|

Re: Segfault when building wxPython with SIP 4.19.11

Phil Thompson-5
In reply to this post by Scott Talbert
On 06/07/2018 14:32, Scott Talbert wrote:

> On Fri, 6 Jul 2018, Phil Thompson wrote:
>
>>>> Hi,
>>>>
>>>> I'm seeing a segfault when building wxPython with SIP 4.19.11.
>>>>
>>>> Running command: sip
>>>> /usr/bin/sip -w -o -g -I /home/talbert/Downloads/wxPython-4.0.1/src
>>>> -I
>>>> /home/talbert/Downloads/wxPython-4.0.1/sip/gen -c /tmp/tmpdH4lfu -b
>>>> sip/cpp/_core.sbf -X pycode_core:wx/core.py sip/gen/_core.sip
>>>> Segmentation fault (core dumped)
>>>>
>>>> (gdb) bt
>>>> #0  prcode (fp=fp@entry=0x55f0f0d13ed0, fmt=0x55f0f042adc7
>>>> "\");\n#else\n",
>>>>     fmt@entry=0x55f0f042ad58 "    /* Get the SIP module's API.
>>>> */\n#if
>>>> PY_VERSION_HEX >= 0x02050000\n    sip_sipmod =
>>>> PyImport_ImportModule(\"%s\");\n#else\n")
>>>>     at ./sipgen/gencode.c:14489
>>>> #1  0x000055f0f04004e6 in generateSipImport (mod=0x55f0f0d14180,
>>>>     fp=0x55f0f0d13ed0, sipName=0x0) at ./sipgen/gencode.c:2775
>>>> #2  generateCpp (pt=pt@entry=0x7ffd5c4cabc0, mod=<optimized out>,
>>>>     codeDir=codeDir@entry=0x7ffd5c4cc455 "/tmp/tmpdH4lfu",
>>>>     srcSuffix=srcSuffix@entry=0x55f0f0422866 ".cpp",
>>>> parts=parts@entry=0,
>>>>     needed_qualifiers=needed_qualifiers@entry=0x0, xsl=0x0,
>>>> py_debug=0,
>>>>     sipName=0x0) at ./sipgen/gencode.c:2561
>>>> #3  0x000055f0f0403269 in generateCode (pt=0x7ffd5c4cabc0,
>>>>     codeDir=0x7ffd5c4cc455 "/tmp/tmpdH4lfu",
>>>>     buildFile=0x7ffd5c4cc467 "sip/cpp/_core.sbf", docFile=<optimized
>>>> out>,
>>>>     srcSuffix=0x55f0f0422866 ".cpp", except=<optimized out>,
>>>> trace=0,
>>>>     releaseGIL=1, parts=0, needed_qualifiers=0x0, xsl=0x0,
>>>> consModule=0x0,
>>>>     docs=1, py_debug=0, sipName=0x0) at ./sipgen/gencode.c:358
>>>> #4  0x000055f0f03e4e15 in main (argc=15, argv=0x7ffd5c4cae58)
>>>>     at ./sipgen/main.c:291
>>>>
>>>> 4.19.8 worked ok.
>>>
>>> It should be fixed in the current snapshot. 4.19.12 will be released
>>> over the weekend.
>>
>> However there are slight changes to the way a private sip module is
>> specified. I don’t know if this affects how wxPython is built.
>
> I don't know either.  When I build wxPython, I am building it for
> Fedora or Debian packages, and I build it using the public sip module,
> stripping out the bundled copy.

How do you know that the two are compatible?

Phil

_______________________________________________
PyQt mailing list    [hidden email]
https://www.riverbankcomputing.com/mailman/listinfo/pyqt
Reply | Threaded
Open this post in threaded view
|

Re: Segfault when building wxPython with SIP 4.19.11

Scott Talbert
On Fri, 6 Jul 2018, Phil Thompson wrote:

>>>>> Hi,
>>>>>
>>>>> I'm seeing a segfault when building wxPython with SIP 4.19.11.
>>>>>
>>>>> Running command: sip
>>>>> /usr/bin/sip -w -o -g -I /home/talbert/Downloads/wxPython-4.0.1/src -I
>>>>> /home/talbert/Downloads/wxPython-4.0.1/sip/gen -c /tmp/tmpdH4lfu -b
>>>>> sip/cpp/_core.sbf -X pycode_core:wx/core.py sip/gen/_core.sip
>>>>> Segmentation fault (core dumped)
>>>>>
>>>>> (gdb) bt
>>>>> #0  prcode (fp=fp@entry=0x55f0f0d13ed0, fmt=0x55f0f042adc7
>>>>> "\");\n#else\n",
>>>>>     fmt@entry=0x55f0f042ad58 "    /* Get the SIP module's API. */\n#if
>>>>> PY_VERSION_HEX >= 0x02050000\n    sip_sipmod =
>>>>> PyImport_ImportModule(\"%s\");\n#else\n")
>>>>>     at ./sipgen/gencode.c:14489
>>>>> #1  0x000055f0f04004e6 in generateSipImport (mod=0x55f0f0d14180,
>>>>>     fp=0x55f0f0d13ed0, sipName=0x0) at ./sipgen/gencode.c:2775
>>>>> #2  generateCpp (pt=pt@entry=0x7ffd5c4cabc0, mod=<optimized out>,
>>>>>     codeDir=codeDir@entry=0x7ffd5c4cc455 "/tmp/tmpdH4lfu",
>>>>>     srcSuffix=srcSuffix@entry=0x55f0f0422866 ".cpp",
>>>>> parts=parts@entry=0,
>>>>>     needed_qualifiers=needed_qualifiers@entry=0x0, xsl=0x0, py_debug=0,
>>>>>     sipName=0x0) at ./sipgen/gencode.c:2561
>>>>> #3  0x000055f0f0403269 in generateCode (pt=0x7ffd5c4cabc0,
>>>>>     codeDir=0x7ffd5c4cc455 "/tmp/tmpdH4lfu",
>>>>>     buildFile=0x7ffd5c4cc467 "sip/cpp/_core.sbf", docFile=<optimized
>>>>> out>,
>>>>>     srcSuffix=0x55f0f0422866 ".cpp", except=<optimized out>, trace=0,
>>>>>     releaseGIL=1, parts=0, needed_qualifiers=0x0, xsl=0x0,
>>>>> consModule=0x0,
>>>>>     docs=1, py_debug=0, sipName=0x0) at ./sipgen/gencode.c:358
>>>>> #4  0x000055f0f03e4e15 in main (argc=15, argv=0x7ffd5c4cae58)
>>>>>     at ./sipgen/main.c:291
>>>>>
>>>>> 4.19.8 worked ok.
>>>>
>>>> It should be fixed in the current snapshot. 4.19.12 will be released
>>>> over the weekend.
>>>
>>> However there are slight changes to the way a private sip module is
>>> specified. I don’t know if this affects how wxPython is built.
>>
>> I don't know either.  When I build wxPython, I am building it for
>> Fedora or Debian packages, and I build it using the public sip module,
>> stripping out the bundled copy.
>
> How do you know that the two are compatible?
That wxPython is compatible with a given version of sip, or whether a
public sip module is compatible with the version of sip that wxPython was
compiled with?

Scott
_______________________________________________
PyQt mailing list    [hidden email]
https://www.riverbankcomputing.com/mailman/listinfo/pyqt
Reply | Threaded
Open this post in threaded view
|

Re: Segfault when building wxPython with SIP 4.19.11

Phil Thompson-5
On 06/07/2018 17:54, Scott Talbert wrote:

> On Fri, 6 Jul 2018, Phil Thompson wrote:
>
>>>>>> Hi,
>>>>>>
>>>>>> I'm seeing a segfault when building wxPython with SIP 4.19.11.
>>>>>>
>>>>>> Running command: sip
>>>>>> /usr/bin/sip -w -o -g -I
>>>>>> /home/talbert/Downloads/wxPython-4.0.1/src -I
>>>>>> /home/talbert/Downloads/wxPython-4.0.1/sip/gen -c /tmp/tmpdH4lfu
>>>>>> -b
>>>>>> sip/cpp/_core.sbf -X pycode_core:wx/core.py sip/gen/_core.sip
>>>>>> Segmentation fault (core dumped)
>>>>>>
>>>>>> (gdb) bt
>>>>>> #0  prcode (fp=fp@entry=0x55f0f0d13ed0, fmt=0x55f0f042adc7
>>>>>> "\");\n#else\n",
>>>>>>     fmt@entry=0x55f0f042ad58 "    /* Get the SIP module's API.
>>>>>> */\n#if
>>>>>> PY_VERSION_HEX >= 0x02050000\n    sip_sipmod =
>>>>>> PyImport_ImportModule(\"%s\");\n#else\n")
>>>>>>     at ./sipgen/gencode.c:14489
>>>>>> #1  0x000055f0f04004e6 in generateSipImport (mod=0x55f0f0d14180,
>>>>>>     fp=0x55f0f0d13ed0, sipName=0x0) at ./sipgen/gencode.c:2775
>>>>>> #2  generateCpp (pt=pt@entry=0x7ffd5c4cabc0, mod=<optimized out>,
>>>>>>     codeDir=codeDir@entry=0x7ffd5c4cc455 "/tmp/tmpdH4lfu",
>>>>>>     srcSuffix=srcSuffix@entry=0x55f0f0422866 ".cpp",
>>>>>> parts=parts@entry=0,
>>>>>>     needed_qualifiers=needed_qualifiers@entry=0x0, xsl=0x0,
>>>>>> py_debug=0,
>>>>>>     sipName=0x0) at ./sipgen/gencode.c:2561
>>>>>> #3  0x000055f0f0403269 in generateCode (pt=0x7ffd5c4cabc0,
>>>>>>     codeDir=0x7ffd5c4cc455 "/tmp/tmpdH4lfu",
>>>>>>     buildFile=0x7ffd5c4cc467 "sip/cpp/_core.sbf",
>>>>>> docFile=<optimized out>,
>>>>>>     srcSuffix=0x55f0f0422866 ".cpp", except=<optimized out>,
>>>>>> trace=0,
>>>>>>     releaseGIL=1, parts=0, needed_qualifiers=0x0, xsl=0x0,
>>>>>> consModule=0x0,
>>>>>>     docs=1, py_debug=0, sipName=0x0) at ./sipgen/gencode.c:358
>>>>>> #4  0x000055f0f03e4e15 in main (argc=15, argv=0x7ffd5c4cae58)
>>>>>>     at ./sipgen/main.c:291
>>>>>>
>>>>>> 4.19.8 worked ok.
>>>>>
>>>>> It should be fixed in the current snapshot. 4.19.12 will be
>>>>> released
>>>>> over the weekend.
>>>>
>>>> However there are slight changes to the way a private sip module is
>>>> specified. I don’t know if this affects how wxPython is built.
>>>
>>> I don't know either.  When I build wxPython, I am building it for
>>> Fedora or Debian packages, and I build it using the public sip
>>> module,
>>> stripping out the bundled copy.
>>
>> How do you know that the two are compatible?
>
> That wxPython is compatible with a given version of sip, or whether a
> public sip module is compatible with the version of sip that wxPython
> was compiled with?

Both.

Phil

_______________________________________________
PyQt mailing list    [hidden email]
https://www.riverbankcomputing.com/mailman/listinfo/pyqt
Reply | Threaded
Open this post in threaded view
|

Re: Segfault when building wxPython with SIP 4.19.11

FeRD
Well, if they aren't, then every effort should be made to make them compatible, right? With some release of the dependency, at least, even if it has to be a specific one. I mean, compatibility only with a particular build that's distributed by the project as an opaque precompiled binary is hardly compatibility at all, from a FLOSS standpoint. Reminds me of the "bad old days" 10 years ago, when every project that used FFmpeg could only be built with the exact source tree that was bundled in with their project, and every project had its own, subtly different build of ffmpeg that they expected to be linked with.

That was awful and made everyone sad, so through herculean effort and endless hacking by both the ffmpeg team and the dependent projects, APIs were matured, callers worked out how to best code against the "stock" libraries, and the situation was slowly evolved to the point where, today, most projects can all be linked with the same stock FFmpeg libs, centrally installed, without requiring hardly any changes at all. It's like living in the future.

Heck, some projects can even be built against a newer release of FFmpeg than the one they were developed with! (Occasionally. Like, if it's one, maybe two releases later, you might have a chance. Their API is still an endlessly moving target, and if you have code that was written for FFmpeg 3.4 and you're already updated to 4.0, you're still Gonna Have A Bad Time™.)

...Anyway, point is, in an ideal world (which is not the world we live in — conceded) the answer to "how do you know it's compatible" would be something as plain as, "Says right in the README, requires version N.M or higher." I guess that's either naive, or optimistic. You decide. (But since you don't know me: smart money's on naive over optimistic.)

On Fri, Jul 6, 2018 at 5:40 PM Phil Thompson <[hidden email]> wrote:
On 06/07/2018 17:54, Scott Talbert wrote:
> On Fri, 6 Jul 2018, Phil Thompson wrote:
>
>>>>>> Hi,
>>>>>>
>>>>>> I'm seeing a segfault when building wxPython with SIP 4.19.11.
>>>>>>
>>>>>> Running command: sip
>>>>>> /usr/bin/sip -w -o -g -I
>>>>>> /home/talbert/Downloads/wxPython-4.0.1/src -I
>>>>>> /home/talbert/Downloads/wxPython-4.0.1/sip/gen -c /tmp/tmpdH4lfu
>>>>>> -b
>>>>>> sip/cpp/_core.sbf -X pycode_core:wx/core.py sip/gen/_core.sip
>>>>>> Segmentation fault (core dumped)
>>>>>>
>>>>>> (gdb) bt
>>>>>> #0  prcode (fp=fp@entry=0x55f0f0d13ed0, fmt=0x55f0f042adc7
>>>>>> "\");\n#else\n",
>>>>>>     fmt@entry=0x55f0f042ad58 "    /* Get the SIP module's API.
>>>>>> */\n#if
>>>>>> PY_VERSION_HEX >= 0x02050000\n    sip_sipmod =
>>>>>> PyImport_ImportModule(\"%s\");\n#else\n")
>>>>>>     at ./sipgen/gencode.c:14489
>>>>>> #1  0x000055f0f04004e6 in generateSipImport (mod=0x55f0f0d14180,
>>>>>>     fp=0x55f0f0d13ed0, sipName=0x0) at ./sipgen/gencode.c:2775
>>>>>> #2  generateCpp (pt=pt@entry=0x7ffd5c4cabc0, mod=<optimized out>,
>>>>>>     codeDir=codeDir@entry=0x7ffd5c4cc455 "/tmp/tmpdH4lfu",
>>>>>>     srcSuffix=srcSuffix@entry=0x55f0f0422866 ".cpp",
>>>>>> parts=parts@entry=0,
>>>>>>     needed_qualifiers=needed_qualifiers@entry=0x0, xsl=0x0,
>>>>>> py_debug=0,
>>>>>>     sipName=0x0) at ./sipgen/gencode.c:2561
>>>>>> #3  0x000055f0f0403269 in generateCode (pt=0x7ffd5c4cabc0,
>>>>>>     codeDir=0x7ffd5c4cc455 "/tmp/tmpdH4lfu",
>>>>>>     buildFile=0x7ffd5c4cc467 "sip/cpp/_core.sbf",
>>>>>> docFile=<optimized out>,
>>>>>>     srcSuffix=0x55f0f0422866 ".cpp", except=<optimized out>,
>>>>>> trace=0,
>>>>>>     releaseGIL=1, parts=0, needed_qualifiers=0x0, xsl=0x0,
>>>>>> consModule=0x0,
>>>>>>     docs=1, py_debug=0, sipName=0x0) at ./sipgen/gencode.c:358
>>>>>> #4  0x000055f0f03e4e15 in main (argc=15, argv=0x7ffd5c4cae58)
>>>>>>     at ./sipgen/main.c:291
>>>>>>
>>>>>> 4.19.8 worked ok.
>>>>>
>>>>> It should be fixed in the current snapshot. 4.19.12 will be
>>>>> released
>>>>> over the weekend.
>>>>
>>>> However there are slight changes to the way a private sip module is
>>>> specified. I don’t know if this affects how wxPython is built.
>>>
>>> I don't know either.  When I build wxPython, I am building it for
>>> Fedora or Debian packages, and I build it using the public sip
>>> module,
>>> stripping out the bundled copy.
>>
>> How do you know that the two are compatible?
>
> That wxPython is compatible with a given version of sip, or whether a
> public sip module is compatible with the version of sip that wxPython
> was compiled with?

Both.

Phil

_______________________________________________
PyQt mailing list    [hidden email]
https://www.riverbankcomputing.com/mailman/listinfo/pyqt

_______________________________________________
PyQt mailing list    [hidden email]
https://www.riverbankcomputing.com/mailman/listinfo/pyqt
Reply | Threaded
Open this post in threaded view
|

Re: Segfault when building wxPython with SIP 4.19.11

Scott Talbert
In reply to this post by Phil Thompson-5
On Fri, 6 Jul 2018, Phil Thompson wrote:

>>>>>>> Hi,
>>>>>>>
>>>>>>> I'm seeing a segfault when building wxPython with SIP 4.19.11.
>>>>>>>
>>>>>>> Running command: sip
>>>>>>> /usr/bin/sip -w -o -g -I /home/talbert/Downloads/wxPython-4.0.1/src -I
>>>>>>> /home/talbert/Downloads/wxPython-4.0.1/sip/gen -c /tmp/tmpdH4lfu -b
>>>>>>> sip/cpp/_core.sbf -X pycode_core:wx/core.py sip/gen/_core.sip
>>>>>>> Segmentation fault (core dumped)
>>>>>>>
>>>>>>> (gdb) bt
>>>>>>> #0  prcode (fp=fp@entry=0x55f0f0d13ed0, fmt=0x55f0f042adc7
>>>>>>> "\");\n#else\n",
>>>>>>>     fmt@entry=0x55f0f042ad58 "    /* Get the SIP module's API. */\n#if
>>>>>>> PY_VERSION_HEX >= 0x02050000\n    sip_sipmod =
>>>>>>> PyImport_ImportModule(\"%s\");\n#else\n")
>>>>>>>     at ./sipgen/gencode.c:14489
>>>>>>> #1  0x000055f0f04004e6 in generateSipImport (mod=0x55f0f0d14180,
>>>>>>>     fp=0x55f0f0d13ed0, sipName=0x0) at ./sipgen/gencode.c:2775
>>>>>>> #2  generateCpp (pt=pt@entry=0x7ffd5c4cabc0, mod=<optimized out>,
>>>>>>>     codeDir=codeDir@entry=0x7ffd5c4cc455 "/tmp/tmpdH4lfu",
>>>>>>>     srcSuffix=srcSuffix@entry=0x55f0f0422866 ".cpp",
>>>>>>> parts=parts@entry=0,
>>>>>>>     needed_qualifiers=needed_qualifiers@entry=0x0, xsl=0x0,
>>>>>>> py_debug=0,
>>>>>>>     sipName=0x0) at ./sipgen/gencode.c:2561
>>>>>>> #3  0x000055f0f0403269 in generateCode (pt=0x7ffd5c4cabc0,
>>>>>>>     codeDir=0x7ffd5c4cc455 "/tmp/tmpdH4lfu",
>>>>>>>     buildFile=0x7ffd5c4cc467 "sip/cpp/_core.sbf", docFile=<optimized
>>>>>>> out>,
>>>>>>>     srcSuffix=0x55f0f0422866 ".cpp", except=<optimized out>, trace=0,
>>>>>>>     releaseGIL=1, parts=0, needed_qualifiers=0x0, xsl=0x0,
>>>>>>> consModule=0x0,
>>>>>>>     docs=1, py_debug=0, sipName=0x0) at ./sipgen/gencode.c:358
>>>>>>> #4  0x000055f0f03e4e15 in main (argc=15, argv=0x7ffd5c4cae58)
>>>>>>>     at ./sipgen/main.c:291
>>>>>>>
>>>>>>> 4.19.8 worked ok.
>>>>>>
>>>>>> It should be fixed in the current snapshot. 4.19.12 will be released
>>>>>> over the weekend.
>>>>>
>>>>> However there are slight changes to the way a private sip module is
>>>>> specified. I don’t know if this affects how wxPython is built.
>>>>
>>>> I don't know either.  When I build wxPython, I am building it for
>>>> Fedora or Debian packages, and I build it using the public sip module,
>>>> stripping out the bundled copy.
>>>
>>> How do you know that the two are compatible?
>>
>> That wxPython is compatible with a given version of sip, or whether a
>> public sip module is compatible with the version of sip that wxPython
>> was compiled with?
>
> Both.
Well, for the first problem, I always make sure that I'm using the
recommended version of sip (or higher).  I suppose there's a possibility
that something could break in a future version of sip, but that generally
hasn't happened.

For the second problem, the public sip module will always be at the same
version as the compiled version or higher.  I'm supposing that by
recommending that sip consumers all use private copies of the module,
you're suggesting that there may be problems (in the future?) where a
newer version of the public module would not function with an older
compiled consumer?

Scott
_______________________________________________
PyQt mailing list    [hidden email]
https://www.riverbankcomputing.com/mailman/listinfo/pyqt
Reply | Threaded
Open this post in threaded view
|

Re: Segfault when building wxPython with SIP 4.19.11

Phil Thompson-5
On 7 Jul 2018, at 2:07 am, Scott Talbert <[hidden email]> wrote:

>
> On Fri, 6 Jul 2018, Phil Thompson wrote:
>
>>>>>>>> Hi,
>>>>>>>> I'm seeing a segfault when building wxPython with SIP 4.19.11.
>>>>>>>> Running command: sip
>>>>>>>> /usr/bin/sip -w -o -g -I /home/talbert/Downloads/wxPython-4.0.1/src -I
>>>>>>>> /home/talbert/Downloads/wxPython-4.0.1/sip/gen -c /tmp/tmpdH4lfu -b
>>>>>>>> sip/cpp/_core.sbf -X pycode_core:wx/core.py sip/gen/_core.sip
>>>>>>>> Segmentation fault (core dumped)
>>>>>>>> (gdb) bt
>>>>>>>> #0  prcode (fp=fp@entry=0x55f0f0d13ed0, fmt=0x55f0f042adc7 "\");\n#else\n",
>>>>>>>>    fmt@entry=0x55f0f042ad58 "    /* Get the SIP module's API. */\n#if
>>>>>>>> PY_VERSION_HEX >= 0x02050000\n    sip_sipmod =
>>>>>>>> PyImport_ImportModule(\"%s\");\n#else\n")
>>>>>>>>    at ./sipgen/gencode.c:14489
>>>>>>>> #1  0x000055f0f04004e6 in generateSipImport (mod=0x55f0f0d14180,
>>>>>>>>    fp=0x55f0f0d13ed0, sipName=0x0) at ./sipgen/gencode.c:2775
>>>>>>>> #2  generateCpp (pt=pt@entry=0x7ffd5c4cabc0, mod=<optimized out>,
>>>>>>>>    codeDir=codeDir@entry=0x7ffd5c4cc455 "/tmp/tmpdH4lfu",
>>>>>>>>    srcSuffix=srcSuffix@entry=0x55f0f0422866 ".cpp", parts=parts@entry=0,
>>>>>>>>    needed_qualifiers=needed_qualifiers@entry=0x0, xsl=0x0, py_debug=0,
>>>>>>>>    sipName=0x0) at ./sipgen/gencode.c:2561
>>>>>>>> #3  0x000055f0f0403269 in generateCode (pt=0x7ffd5c4cabc0,
>>>>>>>>    codeDir=0x7ffd5c4cc455 "/tmp/tmpdH4lfu",
>>>>>>>>    buildFile=0x7ffd5c4cc467 "sip/cpp/_core.sbf", docFile=<optimized out>,
>>>>>>>>    srcSuffix=0x55f0f0422866 ".cpp", except=<optimized out>, trace=0,
>>>>>>>>    releaseGIL=1, parts=0, needed_qualifiers=0x0, xsl=0x0, consModule=0x0,
>>>>>>>>    docs=1, py_debug=0, sipName=0x0) at ./sipgen/gencode.c:358
>>>>>>>> #4  0x000055f0f03e4e15 in main (argc=15, argv=0x7ffd5c4cae58)
>>>>>>>>    at ./sipgen/main.c:291
>>>>>>>> 4.19.8 worked ok.
>>>>>>> It should be fixed in the current snapshot. 4.19.12 will be released
>>>>>>> over the weekend.
>>>>>> However there are slight changes to the way a private sip module is specified. I don’t know if this affects how wxPython is built.
>>>>> I don't know either.  When I build wxPython, I am building it for
>>>>> Fedora or Debian packages, and I build it using the public sip module,
>>>>> stripping out the bundled copy.
>>>> How do you know that the two are compatible?
>>> That wxPython is compatible with a given version of sip, or whether a
>>> public sip module is compatible with the version of sip that wxPython
>>> was compiled with?
>>
>> Both.
>
> Well, for the first problem, I always make sure that I'm using the recommended version of sip (or higher).  I suppose there's a possibility that something could break in a future version of sip, but that generally hasn't happened.
>
> For the second problem, the public sip module will always be at the same version as the compiled version or higher.  I'm supposing that by recommending that sip consumers all use private copies of the module, you're suggesting that there may be problems (in the future?) where a newer version of the public module would not function with an older compiled consumer?

Exactly. The sip module implements an API that has a major.minor version number. Different major versions are, by definition, incompatible. The API version number is completely independent of the version of a sip release.

The whole point of private sip modules is to allow incompatibilities.

Phil
_______________________________________________
PyQt mailing list    [hidden email]
https://www.riverbankcomputing.com/mailman/listinfo/pyqt
Reply | Threaded
Open this post in threaded view
|

Re: Segfault when building wxPython with SIP 4.19.11

Scott Talbert
On Sat, 7 Jul 2018, Phil Thompson wrote:

>>>>>>>>> Hi,
>>>>>>>>> I'm seeing a segfault when building wxPython with SIP 4.19.11.
>>>>>>>>> Running command: sip
>>>>>>>>> /usr/bin/sip -w -o -g -I /home/talbert/Downloads/wxPython-4.0.1/src -I
>>>>>>>>> /home/talbert/Downloads/wxPython-4.0.1/sip/gen -c /tmp/tmpdH4lfu -b
>>>>>>>>> sip/cpp/_core.sbf -X pycode_core:wx/core.py sip/gen/_core.sip
>>>>>>>>> Segmentation fault (core dumped)
>>>>>>>>> (gdb) bt
>>>>>>>>> #0  prcode (fp=fp@entry=0x55f0f0d13ed0, fmt=0x55f0f042adc7 "\");\n#else\n",
>>>>>>>>>    fmt@entry=0x55f0f042ad58 "    /* Get the SIP module's API. */\n#if
>>>>>>>>> PY_VERSION_HEX >= 0x02050000\n    sip_sipmod =
>>>>>>>>> PyImport_ImportModule(\"%s\");\n#else\n")
>>>>>>>>>    at ./sipgen/gencode.c:14489
>>>>>>>>> #1  0x000055f0f04004e6 in generateSipImport (mod=0x55f0f0d14180,
>>>>>>>>>    fp=0x55f0f0d13ed0, sipName=0x0) at ./sipgen/gencode.c:2775
>>>>>>>>> #2  generateCpp (pt=pt@entry=0x7ffd5c4cabc0, mod=<optimized out>,
>>>>>>>>>    codeDir=codeDir@entry=0x7ffd5c4cc455 "/tmp/tmpdH4lfu",
>>>>>>>>>    srcSuffix=srcSuffix@entry=0x55f0f0422866 ".cpp", parts=parts@entry=0,
>>>>>>>>>    needed_qualifiers=needed_qualifiers@entry=0x0, xsl=0x0, py_debug=0,
>>>>>>>>>    sipName=0x0) at ./sipgen/gencode.c:2561
>>>>>>>>> #3  0x000055f0f0403269 in generateCode (pt=0x7ffd5c4cabc0,
>>>>>>>>>    codeDir=0x7ffd5c4cc455 "/tmp/tmpdH4lfu",
>>>>>>>>>    buildFile=0x7ffd5c4cc467 "sip/cpp/_core.sbf", docFile=<optimized out>,
>>>>>>>>>    srcSuffix=0x55f0f0422866 ".cpp", except=<optimized out>, trace=0,
>>>>>>>>>    releaseGIL=1, parts=0, needed_qualifiers=0x0, xsl=0x0, consModule=0x0,
>>>>>>>>>    docs=1, py_debug=0, sipName=0x0) at ./sipgen/gencode.c:358
>>>>>>>>> #4  0x000055f0f03e4e15 in main (argc=15, argv=0x7ffd5c4cae58)
>>>>>>>>>    at ./sipgen/main.c:291
>>>>>>>>> 4.19.8 worked ok.
>>>>>>>> It should be fixed in the current snapshot. 4.19.12 will be released
>>>>>>>> over the weekend.
>>>>>>> However there are slight changes to the way a private sip module is specified. I don’t know if this affects how wxPython is built.
>>>>>> I don't know either.  When I build wxPython, I am building it for
>>>>>> Fedora or Debian packages, and I build it using the public sip module,
>>>>>> stripping out the bundled copy.
>>>>> How do you know that the two are compatible?
>>>> That wxPython is compatible with a given version of sip, or whether a
>>>> public sip module is compatible with the version of sip that wxPython
>>>> was compiled with?
>>>
>>> Both.
>>
>> Well, for the first problem, I always make sure that I'm using the recommended version of sip (or higher).  I suppose there's a possibility that something could break in a future version of sip, but that generally hasn't happened.
>>
>> For the second problem, the public sip module will always be at the same version as the compiled version or higher.  I'm supposing that by recommending that sip consumers all use private copies of the module, you're suggesting that there may be problems (in the future?) where a newer version of the public module would not function with an older compiled consumer?
>
> Exactly. The sip module implements an API that has a major.minor version
> number. Different major versions are, by definition, incompatible. The
> API version number is completely independent of the version of a sip
> release.
>
> The whole point of private sip modules is to allow incompatibilities.
Ah.  Well, in general I believe the Fedora sip package maintainers won't
allow a sip API version change in a Fedora stable release, so I think this
generally avoids problems.  I suspect Debian does the same.  It's mainly a
concern in the development branches (rawhide/unstable).

Scott
_______________________________________________
PyQt mailing list    [hidden email]
https://www.riverbankcomputing.com/mailman/listinfo/pyqt