[issue40019] test_gdb should better detect when Python is optimized

STINNER Victor added the comment: Ok, test_gdb should now be more reliable with various compilers and compiler optimization levels. I chose to not skip a test if '' is found in the gdb output. If it becomes an issue, test_gdb can easily be modified to also be skipped in this case.

[issue40019] test_gdb should better detect when Python is optimized

miss-islington added the comment: New changeset a764a1cc663708361300cdf88fcf697633142319 by Miss Islington (bot) in branch '3.7': bpo-40019: Skip test_gdb if Python was optimized (GH-19081) https://github.com/python/cpython/commit/a764a1cc663708361300cdf88fcf697633142319 -- ___

[issue40019] test_gdb should better detect when Python is optimized

miss-islington added the comment: New changeset 4ced9a7611ddfd923bd8f72aa61121d0e5aeb8fc by Miss Islington (bot) in branch '3.8': bpo-40019: Skip test_gdb if Python was optimized (GH-19081) https://github.com/python/cpython/commit/4ced9a7611ddfd923bd8f72aa61121d0e5aeb8fc -- ___

[issue40019] test_gdb should better detect when Python is optimized

STINNER Victor added the comment: We have this issue in Fedora Rawhide. test_gdb of Python 3.8 fails on s390x and armv7hl architectures with GCC 10: https://bugzilla.redhat.com/show_bug.cgi?id=1818857 I tested manually that my change fix test_gdb: tests are skipped as expected: https://src.fe

[issue40019] test_gdb should better detect when Python is optimized

Change by miss-islington : -- pull_requests: +18614 pull_request: https://github.com/python/cpython/pull/19256 ___ Python tracker ___ __

[issue40019] test_gdb should better detect when Python is optimized

Change by miss-islington : -- nosy: +miss-islington nosy_count: 1.0 -> 2.0 pull_requests: +18613 pull_request: https://github.com/python/cpython/pull/19255 ___ Python tracker _

[issue40019] test_gdb should better detect when Python is optimized

STINNER Victor added the comment: The fix works as expected: test_gdb passed on PR 19077. Well, likely because a few tests have been skipped. I don't think that in test_gdb can do better than skipping the test if gdb fails to read debug information. -- __

[issue40019] test_gdb should better detect when Python is optimized

STINNER Victor added the comment: New changeset 7bf069b6110278102c8f4719975a5eb5a5af25f9 by Victor Stinner in branch 'master': bpo-40019: Skip test_gdb if Python was optimized (GH-19081) https://github.com/python/cpython/commit/7bf069b6110278102c8f4719975a5eb5a5af25f9 -- __

[issue40019] test_gdb should better detect when Python is optimized

Change by STINNER Victor : -- keywords: +patch pull_requests: +18440 stage: -> patch review pull_request: https://github.com/python/cpython/pull/19081 ___ Python tracker ___ _

[issue40019] test_gdb should better detect when Python is optimized

New submission from STINNER Victor : On my PR 19077 which changes Python/ceval.c, test_gdb fails on Travis CI with Python compiled with clang -Og. The -Og optimization level is a compromise between performance and the ability to debug Python. The problem is that gdb fails to retrieve some inf