New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
python2.1b1 core dumps --with-pymalloc #34115
Comments
% ./configure --without-threads --with-pymalloc ./python setup.py |
Logged In: YES Alas, I can't reproduce this on Linux. I'm afraid building Python on HP-UX is braindead, and I So, while I am sympathetic, I can't help. Somebody else |
Logged In: NO [213] % gcc --version If I build Objects/obmalloc.w WITHOUT the -O2 option then If I build Objects/obmalloc.w WITH the -O2 (the default) [212] % gdb ./python ./setup.py build Program received signal SIGBUS, Bus error. |
Logged In: NO With an updated version of gcc it (python2.1b1) still fails % gcc --version Program received signal SIGSEGV, Segmentation fault. If I remove the -O2 when compiling Objects/object.o then |
Logged In: NO Downloaded python2.1beta2. Used gcc 2.95.3 on HPUX 10.2 This time it blew up in different manner: /bin/sh: 22414 Abort Removed Objects/object.o and rebuilt it without the -O2 |
Logged In: YES I'm closing this -- it seems to be a compiler problem. The moral of the story: turn off -O2 when you're |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: