[issue19743] test_gdb failures

2014-08-10 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue19743] test_gdb failures

2014-08-10 Thread Mark Lawrence
Mark Lawrence added the comment: Seems as if this can be closed. -- nosy: +BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mai

[issue19743] test_gdb failures

2013-11-25 Thread Larry Hastings
Larry Hastings added the comment: If skipping them for optimized builds is the right call, then aren't we done here? Can we close this bug as fixed? -- ___ Python tracker ___ _

[issue19743] test_gdb failures

2013-11-25 Thread Dave Malcolm
Dave Malcolm added the comment: FWIW, I feel that it's worth just expecting failures with an *optimized* build: with an optimizing compiler, there's likely to always be some program counter location where the debugger is going to get confused for some variables. Given umpteen different compil

[issue19743] test_gdb failures

2013-11-24 Thread Larry Hastings
Larry Hastings added the comment: Antoine: your checked-in workaround makes the test pass. But I'm leaving this open because I'm still hoping David will take a look into it. -- ___ Python tracker

[issue19743] test_gdb failures

2013-11-24 Thread Antoine Pitrou
Antoine Pitrou added the comment: Agreed. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue19743] test_gdb failures

2013-11-24 Thread Larry Hastings
Larry Hastings added the comment: Sorry, both exceptions in the output of the traceback are: Python Exception 'utf-8' codec can't decode byte 0x80 in position 0: invalid start byte: -- ___ Python tracker ___

[issue19743] test_gdb failures

2013-11-24 Thread Larry Hastings
Larry Hastings added the comment: Here's what I've figured out. If I build trunk then run: % gdb --batch -iex "add-auto-load-safe-path /home/larry/src/python/buildtrunk/python-gdb.py" --eval-command="set breakpoint pending yes" --eval-command="break builtin_id" --eval-command=run --eval-comm

[issue19743] test_gdb failures

2013-11-24 Thread Roundup Robot
Roundup Robot added the comment: New changeset e42b449f73fd by Antoine Pitrou in branch '3.3': Issue #19743: fix test_gdb on some optimized Python builds http://hg.python.org/cpython/rev/e42b449f73fd -- ___ Python tracker

[issue19743] test_gdb failures

2013-11-24 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- nosy: +dmalcolm ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyt

[issue19743] test_gdb failures

2013-11-24 Thread Roundup Robot
Roundup Robot added the comment: New changeset 7a14cde3c4df by Antoine Pitrou in branch 'default': Issue #19743: fix test_gdb on some optimized Python builds http://hg.python.org/cpython/rev/7a14cde3c4df -- nosy: +python-dev ___ Python tracker

[issue19743] test_gdb failures

2013-11-23 Thread Larry Hastings
Larry Hastings added the comment: The test passes if I turn on "--with-pydebug". And Antoine told me in IRC that he sees the failure if he turns off "--with-pydebug". So we're in business. -- ___ Python tracker

[issue19743] test_gdb failures

2013-11-23 Thread Antoine Pitrou
Antoine Pitrou added the comment: Ok, it seems the failures are due to a non-pydebug build. I'll investigate tomorrow. -- ___ Python tracker ___

[issue19743] test_gdb failures

2013-11-23 Thread Larry Hastings
Larry Hastings added the comment: That's correct, it is skipped. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue19743] test_gdb failures

2013-11-23 Thread Antoine Pitrou
Antoine Pitrou added the comment: If you go back one revision, test_gdb isn't run at all, right? (it should be skipped) -- ___ Python tracker ___

[issue19743] test_gdb failures

2013-11-23 Thread Larry Hastings
Larry Hastings added the comment: The first bad revision is: changeset: 87426:9f2a0043396b user:Antoine Pitrou date:Sat Nov 23 17:40:36 2013 +0100 files: Lib/test/test_gdb.py Tools/gdb/libpython.py description: Issue #19308: fix the gdb plugin on gdbs linked with Python 3

[issue19743] test_gdb failures

2013-11-23 Thread Larry Hastings
Larry Hastings added the comment: Please see the attached output from the test run. But here's a sample: == FAIL: test_lists (test.test_gdb.PrettyPrintTests) Verify the pretty-printing of lists -

[issue19743] test_gdb failures

2013-11-23 Thread Antoine Pitrou
Antoine Pitrou added the comment: > test_gdb started failing on me within the past few days Can you please bisect to find the offending changeset? -- ___ Python tracker ___

[issue19743] test_gdb failures

2013-11-23 Thread Larry Hastings
New submission from Larry Hastings: test_gdb started failing on me within the past few days. (I would have reported it sooner but I figured the omniscient CPython core dev community already knew about it.) The machine it's failing on is Ubuntu 13.10, 64-bit. -- components: Tests file