[issue40436] pythoninfo collect_gdb() blows up when gdb fails to run

2020-06-11 Thread STINNER Victor
STINNER Victor added the comment: I marked bpo-29685 "test_gdb failed" as duplicate of this issue. Extract: (...) File "/home/studio/Python-3.6.0/Lib/test/test_gdb.py", line 46, in gdb_version, gdb_major_version, gdb_minor_version = get_gdb_version() File "/home/studio/Python-3.6.0/Li

[issue40436] pythoninfo collect_gdb() blows up when gdb fails to run

2020-04-29 Thread STINNER Victor
STINNER Victor added the comment: Thanks Miro for the bug report, it's now fixed ;-) In PR 19792, Miro proposed to skip test_gdb is gdb is available but exit with non-zero exit code. I chose to raise a hard exception instead, to notify CI owners that something is wrong. I prefer to not make

[issue40436] pythoninfo collect_gdb() blows up when gdb fails to run

2020-04-29 Thread miss-islington
miss-islington added the comment: New changeset beba1a808000d5fc445cb28eab96bdb4cdb7c959 by Miss Islington (bot) in branch '3.7': bpo-40436: Fix code parsing gdb version (GH-19792) https://github.com/python/cpython/commit/beba1a808000d5fc445cb28eab96bdb4cdb7c959 --

[issue40436] pythoninfo collect_gdb() blows up when gdb fails to run

2020-04-29 Thread miss-islington
miss-islington added the comment: New changeset d9e904919197a22b95946f11ba5f24b796088c06 by Miss Islington (bot) in branch '3.8': bpo-40436: Fix code parsing gdb version (GH-19792) https://github.com/python/cpython/commit/d9e904919197a22b95946f11ba5f24b796088c06 --

[issue40436] pythoninfo collect_gdb() blows up when gdb fails to run

2020-04-29 Thread STINNER Victor
STINNER Victor added the comment: I fixed test.pythoninfo to ignore gdb output if the command failed. I also enhanced test_gdb error message: display stdout, stderr and the exit code. Backport to 3.8 and 3.7 will be merged as soon as the CI pass. -- resolution: -> fixed stage: patch

[issue40436] pythoninfo collect_gdb() blows up when gdb fails to run

2020-04-29 Thread miss-islington
Change by miss-islington : -- pull_requests: +19117 pull_request: https://github.com/python/cpython/pull/19796 ___ Python tracker ___ __

[issue40436] pythoninfo collect_gdb() blows up when gdb fails to run

2020-04-29 Thread miss-islington
Change by miss-islington : -- nosy: +miss-islington nosy_count: 2.0 -> 3.0 pull_requests: +19116 pull_request: https://github.com/python/cpython/pull/19795 ___ Python tracker _

[issue40436] pythoninfo collect_gdb() blows up when gdb fails to run

2020-04-29 Thread STINNER Victor
STINNER Victor added the comment: New changeset ec9bea4a3766bd815148a27f61eb24e7dd459ac7 by Victor Stinner in branch 'master': bpo-40436: Fix code parsing gdb version (GH-19792) https://github.com/python/cpython/commit/ec9bea4a3766bd815148a27f61eb24e7dd459ac7 -- ___

[issue40436] pythoninfo collect_gdb() blows up when gdb fails to run

2020-04-29 Thread Miro Hrončok
Miro Hrončok added the comment: BTW The test gdb also crashes in the same way: test test_gdb crashed -- Traceback (most recent call last): File "/builddir/build/BUILD/Python-3.9.0a6/Lib/test/libregrtest/runtest.py", line 270, in _runtest_inner refleak = _runtest_inner2(ns, test_name) F

[issue40436] pythoninfo collect_gdb() blows up when gdb fails to run

2020-04-29 Thread STINNER Victor
Change by STINNER Victor : -- keywords: +patch pull_requests: +19114 stage: -> patch review pull_request: https://github.com/python/cpython/pull/19792 ___ Python tracker ___ _

[issue40436] pythoninfo collect_gdb() blows up when gdb fails to run

2020-04-29 Thread Miro Hrončok
New submission from Miro Hrončok : We had this weird traceback when running pythoninfo in Fedora build with Python 3.9.0a6: + /builddir/build/BUILD/Python-3.9.0a6/build/optimized/python -m test.pythoninfo ERROR: collect_gdb() failed Traceback (most recent call last): File "/builddir/build/BUI