This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: What could cause this SEGV
On 06/12/2018 02:16 PM, Paul Smith wrote:
> Also the working .so runs correctly on all the systems, and the failing
> .so fails on all the systems (even the one it was created on).
>
> FWIW, the failing .so is a Python 2.7 module which is part of the
> Pycrypto package: it's _fastmath.so which links in a static GNU MPIR
> 3.0.0 library and is dlopen()'d by Python. When it fails it dumps core
> in the __gmpz_init() function. Unfortunately I have nowhere near
> sufficient assembly fu to investigate much more than that.
>
> Is there more I could do to track this down and understand it? Should
> I just proceed with the "working" _fastmath.so and call it good? It
> seems like there's some hole in my encapsulation that I can't see; I
> would prefer to find and patch it if possible...
It might be related to ordering. There very probably is something
really wrong, so I think it deserves more investigation. However,
I think you really have to debug it. gdb is your friend.
--
Andrew Haley
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671