[issue11994] [2.7/gcc-4.4.3] Segfault under valgrind in string.split()

STINNER Victor added the comment: GCC does have bugs: see a recent example with a development version of GCC 4.6 => #9880 (the bug was fixed before the final release of GCC 4.6). If you would like to go futher, you should open a bug report in GCC bug tracker (not in the Python bug tracker).

[issue11994] [2.7/gcc-4.4.3] Segfault under valgrind in string.split()

Stefan Krah added the comment: The segfault also occurs with a self-compiled gcc-4.4.6, but not with gcc-4.5.3. -- ___ Python tracker ___ ___

[issue11994] [2.7/gcc-4.4.3] Segfault under valgrind in string.split()

Stefan Krah added the comment: Terry J. Reedy wrote: > "Also, the segfault only occurs when python is > compiled with optimizations and run under valgrind." > > This says to me that the segfault is not a Python issue. > What change do you expect in the Python source code? > If none, this issue

[issue11994] [2.7/gcc-4.4.3] Segfault under valgrind in string.split()

Terry J. Reedy added the comment: "Also, the segfault only occurs when python is compiled with optimizations and run under valgrind." This says to me that the segfault is not a Python issue. What change do you expect in the Python source code? If none, this issue should be closed. -- n

[issue11994] [2.7/gcc-4.4.3] Segfault under valgrind in string.split()

STINNER Victor added the comment: GCC 4.4.3 is not the last stable version of the 4.4 branch: try maybe GCC 4.4.6... Changes of GCC 4.4.4, 4.4.5 and 4.4.6: http://gcc.gnu.org/gcc-4.4/changes.html#4.4.6 Or try maybe another major version. -- ___ Py

[issue11994] [2.7/gcc-4.4.3] Segfault under valgrind in string.split()

Stefan Krah added the comment: STINNER Victor wrote: > You should try to disable compiler optimization: pass -O0 to gcc. E.g. use > ./configure --with-pydebug CFLAGS="-O0". I did, see "only occurs when python is compiled with optimizations". :) -- ___

[issue11994] [2.7/gcc-4.4.3] Segfault under valgrind in string.split()

Changes by Daniel Stutzbach : -- nosy: +stutzbach ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue11994] [2.7/gcc-4.4.3] Segfault under valgrind in string.split()

STINNER Victor added the comment: > I can reproduce this only with gcc-4.4.3, so it could also be a compiler bug. You should try to disable compiler optimization: pass -O0 to gcc. E.g. use ./configure --with-pydebug CFLAGS="-O0". -- nosy: +haypo __

[issue11994] [2.7/gcc-4.4.3] Segfault under valgrind in string.split()

New submission from Stefan Krah : I can reproduce this only with gcc-4.4.3, so it could also be a compiler bug. Also, the segfault only occurs when python is compiled with optimizations and run under valgrind. hg up 2.7 make distclean ./configure make valgrind --suppressions=Misc/valgrind-pytho