Tom Morris tfmor...@gmail.com added the comment:
Sorry, I misread the 'version' field as the version the fix was committed for,
not the version the bug was reported against.
The fix was reportedly fixed in r82648 and v2.7 is r82500. If there's ever a
2.7.1, I guess the fix will appear, but
Tom Morris tfmor...@gmail.com added the comment:
Did this fix actually make the 2.7 release? I just installed 2.7 on 64-bit
Ubuntu and ran into the same problem.
python -c import sysconfig; print sysconfig.get_config_vars()['PY_CFLAGS']
-fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3
Martin v. Löwis mar...@v.loewis.de added the comment:
Did this fix actually make the 2.7 release?
Are you sure you posted to the right issue? I fail to see the
relationship between your message and the original report.
If you found a bug in Python 2.7, please report it as a
separate issue.
Dave Malcolm dmalc...@redhat.com added the comment:
This should be fixed now that issue 8605 is resolved: we now skip test_gdb if
the compiler optimization level is above -O0
--
resolution: - fixed
stage: - committed/rejected
___
Python tracker
Changes by Dave Malcolm dmalc...@redhat.com:
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9163
___
___
Python-bugs-list
Dave Malcolm dmalc...@redhat.com added the comment:
Deciphering the output from the assertion, the stdout from gdb when running the
test was:
--- BEGIN ---
Breakpoint 1, PyObject_Print (op=42, fp=0x401cf4e0, flags=1) at
Objects/object.c:329
329 {
#3 Frame 0x81e322c, for file
Michael Blume blume.m...@gmail.com added the comment:
The commands I issued to build were just
./configure
make
make install
These machines were both fairly vanilla setups, so I don't think there should
have been any strange flags going to the compiler.
--
Michael Blume blume.m...@gmail.com added the comment:
-fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes
-I. -IInclude -I./Include -DPy_BUILD_CORE
--
___
Python tracker rep...@bugs.python.org
Dave Malcolm dmalc...@redhat.com added the comment:
Thanks for the info. The final optimization option passed to gcc is the -O3,
so the build was done with optimization.
It's not going to be possible to determine if and when gdb will be able to work
in an optimized build across all different
New submission from Michael Blume blume.m...@gmail.com:
After building Python 2.7 on two separate X68 Ubuntu boxes, test_gdb failed
both times.
./configure
make
make test
output follows:
test_gdb
test test_gdb failed -- Traceback (most recent call last):
File
Martin v. Löwis mar...@v.loewis.de added the comment:
Dave, can you please take a look?
--
assignee: - dmalcolm
nosy: +dmalcolm, loewis
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9163
11 matches
Mail list logo
