[issue5023] Segfault in datetime.time.strftime("%z")

Changes by Alexander Belopolsky : -- status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: h

[issue5023] Segfault in datetime.time.strftime("%z")

Alexander Belopolsky added the comment: Since no one is able to reproduce this crash, I am going to close this issue. -- status: open -> pending ___ Python tracker ___ __

[issue5023] Segfault in datetime.time.strftime("%z")

Eric Wald added the comment: Reproduced again in version 2.7rc2; I had thought that it went away, but it turns out that --with-pydebug hides the problem. Compiling GDB now. -- status: pending -> open versions: +Python 2.7 ___ Python tracker

[issue5023] Segfault in datetime.time.strftime("%z")

Alexander Belopolsky added the comment: Since this does not seem to be reproducible anymore, I am going to close this soon. -- resolution: -> works for me status: open -> pending ___ Python tracker __

[issue5023] Segfault in datetime.time.strftime("%z")

Philipp Gortan added the comment: Unfortunately, I'm no longer able to reproduce this issue as I upgraded to gcc 4.3 sometime within the last nine months... With 4.3, I don't see this segfault any longer. -- ___ Python tracker

[issue5023] Segfault in datetime.time.strftime("%z")

Alexander Belopolsky added the comment: Philipp, Why do you think you see the same problem as Eric? Can you set a trace on &tuple and see when it gets modified? Do you see the crash with zone_failure.py, test_datetime.py or both? -- ___ Python tra

[issue5023] Segfault in datetime.time.strftime("%z")

Philipp Gortan added the comment: @belopolsky: unittest exists, /usr/lib/python2.6/test/test_datetime.py as mentioned by the OP, this unittest reproduces the issue. -- ___ Python tracker __

[issue5023] Segfault in datetime.time.strftime("%z")

Changes by Alexander Belopolsky : -- stage: -> unit test needed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue5023] Segfault in datetime.time.strftime("%z")

Changes by Alexander Belopolsky : -- assignee: -> belopolsky nosy: +belopolsky ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue5023] Segfault in datetime.time.strftime("%z")

Philipp Gortan added the comment: I can reproduce this problem with Gentoo Hardened and gcc version 3.4.6 (Gentoo Hardened 3.4.6-r2 p1.6, ssp-3.4.6-1.0, pie-8.7.10) when gdb-ing through the datetimemodule.c, and displaying the "tuple" variable in time_strftime, I can see that the pointer gets

[issue5023] Segfault in datetime.time.strftime("%z")

Neal Norwitz added the comment: Can you debug this problem any further? What is the C call stack? Does the problem occur if you build in debug mode (./configure --with-pydebug)? Does the problem occur with a different compiler (if you have access to another one on the same box)? -- n

[issue5023] Segfault in datetime.time.strftime("%z")

Eric Wald added the comment: Update: Undefining HAVE_SNPRINTF does not correct the problem. ___ Python tracker ___ ___ Python-bugs-list mailing

[issue5023] Segfault in datetime.time.strftime("%z")

New submission from Eric Wald : Execution of "make test" for Python 2.6.1 halts with a segmentation fault on line 2198 of Python-2.6.1/Lib/test/test_datetime.py; also occurs using the attached script, narrowing it down to the %z sequence in the format argument to datetime.time.strftime(), but