Message332501
I can also confirm that the included patch does "workaround" the issue.
A big pain point here for me is in determining what exit handler is causing this.
GDB has been it's usual great help in determining information about the exact segfault, but the problem code itself is rather elusive since it's ran so much earlier and just causes this issue downstream later in execution. Unfortunately the extensions I'm dealing with also happen to take a lifetime to compile, exacerbated by the fact that they are dependent upon one another.
Can we please apply this to 3.x's tree? |
|
Date |
User |
Action |
Args |
2018-12-25 00:51:37 | trevorj | set | recipients:
+ trevorj, lemburg, amaury.forgeotdarc, pitrou, vstinner, larry, benjamin.peterson, ned.deily, python-dev, m_python, flex.plexico, Stian Lode |
2018-12-25 00:51:35 | trevorj | set | messageid: <1545699095.34.0.712150888896.issue17703@roundup.psfhosted.org> |
2018-12-25 00:51:35 | trevorj | link | issue17703 messages |
2018-12-25 00:51:35 | trevorj | create | |
|