[issue8330] Failures seen in test_gdb on buildbots

Dave Malcolm added the comment: Oops; closing. Thanks. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Pyt

[issue8330] Failures seen in test_gdb on buildbots

Antoine Pitrou added the comment: Shouldn't this be closed? -- nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue8330] Failures seen in test_gdb on buildbots

Martin v. Löwis added the comment: I have now applied file16808 as r79986. I'm detaching file16804, as it was superceded by the other patch. I also reenabled all tests in r79987, to see how the buildbots react. -- ___ Python tracker

[issue8330] Failures seen in test_gdb on buildbots

Changes by Dave Malcolm : -- nosy: +loewis ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue8330] Failures seen in test_gdb on buildbots

Dave Malcolm added the comment: Both of the failing tests use "set" inside gdb to try to corrupt the memory of the inferior process. I believe the issue here is that reading through 0xDEADBEEF within gdb on this machine isn't generating a RuntimeError; perhaps that _is_ a valid pointer in th

[issue8330] Failures seen in test_gdb on buildbots

Dave Malcolm added the comment: There's also a deprecation warning in that log: /home/doko/buildarea/trunk.klose-debian-alpha/build/Lib/test/test_gdb.py:229: DeprecationWarning: BaseException.message has been deprecated as of Python 2.6 if e.message != 'unichr() arg not in range(0x1) (nar

[issue8330] Failures seen in test_gdb on buildbots

New submission from Dave Malcolm : http://www.python.org/dev/buildbot/trunk/builders/alpha%20Debian%20trunk/builds/52/steps/test/logs/stdio shows some failures in test_gdb: == FAIL: test_corrupt_ob_type (test.test_gdb.PrettyPrin