[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

STINNER Victor added the comment: I'm fine with relying on buildbots for test_gdb on Python 3.7 and older. Thanks for the fixes. -- ___ Python tracker ___ ___

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

miss-islington added the comment: New changeset 60f24b23bf6ac485d195bb904635bdc3fe646b07 by Miss Islington (bot) in branch '3.8': bpo-30345: travis: use -Og with --with-pydebug (GH-14423) https://github.com/python/cpython/commit/60f24b23bf6ac485d195bb904635bdc3fe646b07 -- nosy: +mis

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

Inada Naoki added the comment: I think test_gdb is useful for 3.8 branch because some PEP 590 relating changes will be backported to it. But I don't know how test_gdb is useful for older branches. -- ___ Python tracker

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

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

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

Inada Naoki added the comment: New changeset 21cfae107e410bf4b0ab3c142ca4449bc33290f5 by Inada Naoki in branch 'master': bpo-30345: travis: use -Og with --with-pydebug (GH-14423) https://github.com/python/cpython/commit/21cfae107e410bf4b0ab3c142ca4449bc33290f5 -- __

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

Change by Inada Naoki : -- pull_requests: +14239 pull_request: https://github.com/python/cpython/pull/14423 ___ Python tracker ___ _

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

STINNER Victor added the comment: > I created backports to 2.7, 3.6 and 3.7 branches: do you see any reason to > not fix python-gdb.py in these branches? (Any reason to not add -g to > $LTOFLAGS?) Honestly, the risk is very low: only "./configure --with-lto" is impacted and the addition of

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

STINNER Victor added the comment: New changeset 319cfb5f30c2f5da0cdcd556574727ca347cb7de by Victor Stinner in branch '2.7': bpo-30345: Add -g to LDFLAGS for LTO (GH-7709) (GH-7825) https://github.com/python/cpython/commit/319cfb5f30c2f5da0cdcd556574727ca347cb7de --

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

STINNER Victor added the comment: New changeset 78392885c9b08021c89649728053d31503d8a509 by Victor Stinner in branch '3.6': bpo-30345: Add -g to LDFLAGS for LTO (GH-7709) (GH-7826) https://github.com/python/cpython/commit/78392885c9b08021c89649728053d31503d8a509 --

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

STINNER Victor added the comment: New changeset 1bb9dd337ed5aa9eafc8e2ce017ceedf044145e3 by Victor Stinner (Miss Islington (bot)) in branch '3.7': bpo-30345: Add -g to LDFLAGS for LTO (GH-7709) (GH-7824) https://github.com/python/cpython/commit/1bb9dd337ed5aa9eafc8e2ce017ceedf044145e3 -

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

Change by STINNER Victor : -- pull_requests: +7433 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

STINNER Victor added the comment: I created backports to 2.7, 3.6 and 3.7 branches: do you see any reason to not fix python-gdb.py in these branches? (Any reason to not add -g to $LTOFLAGS?) -- nosy: +inada.naoki, pitrou ___ Python tracker

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

Change by STINNER Victor : -- pull_requests: +7432 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

Change by miss-islington : -- pull_requests: +7431 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

STINNER Victor added the comment: Ok, I pushed a change to the master branch. Now the question is if Python 2.7, 3.6 and 3.7 should be fixed as well? I will wait at least one day to see if buildbots are happy. -- ___ Python tracker

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

STINNER Victor added the comment: New changeset 06fe77a84bd29d51506ab2ff703ae585a6121af2 by Victor Stinner in branch 'master': bpo-30345: Add -g to LDFLAGS for LTO (GH-7709) https://github.com/python/cpython/commit/06fe77a84bd29d51506ab2ff703ae585a6121af2 -- ___

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

STINNER Victor added the comment: Very interesting article about PGO and LTO changes in GCC: https://hubicka.blogspot.com/2018/06/gcc-8-link-time-and-interprocedural.html See "Early debug info" paragraph. -- ___ Python tracker

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

STINNER Victor added the comment: > Except for py-bt, you should also try bt. Oh. Using PGO+LTO but without LDFLAGS=-g, bt only shows me function names: all arguments are missing. I tested with LDFLAGS=-g: py-bt and bt work as expected, and test_gdb pass. I created PR 7709 to always compile

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

Change by STINNER Victor : -- keywords: +patch pull_requests: +7323 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-l

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

Change by Marcel Plch : -- nosy: +petr.viktorin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

Marcel Plch added the comment: Those -g switches you see there are during compile-time. For this to work, you need to enable it also during link/time: ./configure --enable-optimizations --with-lto LDFLAGS="-g" Except for py-bt, you should also try bt. With this link flag enabled, I can observ

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

STINNER Victor added the comment: I tested on the current master: git clean -fdx ./configure --with-lto --enable-optimizations sed -i -e 's/^PROFILE_TASK=.*/PROFILE_TASK=-c pass/' Makefile make 2>&1|tee log Python is compiled twice: * (1) gcc -DNDEBUG -g -O3 -flto -fprofile-generate (...) *

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

Marcel Plch added the comment: Yes, but that is not a fix really in this case. While it makes the test pass because it 'correctly' prints out unknown objects, it makes no real difference when actually debugging. The -g switch at link time makes the debug symbols readable and user is able to d

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

STINNER Victor added the comment: > - ["Python Exception Variable 'func_obj' not found.: ", bpo-32962: My commit 019d33b7a447e78057842332fb5d3bad01922122 "python-gdb catchs ValueError on read_var()" (PR 7692) catches this ValueError. -- ___ Pytho

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

Marcel Plch added the comment: LTO may break the debug symbols and make GDB unusable. There is an option, that fixes the issue: to use a -g switch in link flags. Note that this slows loading of the debug symbols significantly. I suggest these options as possible approaches: 1) make the config

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

Change by Matej Cepl : -- nosy: +mcepl ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.or

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

Changes by Kubilay Kocak : -- nosy: +koobs ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

Mikhail added the comment: So, I tried the modified patch (see http://aldan.algebra.com/~mi/tmp/patch-issue30345) -- and now I simply get a different variable name in the error-message: (gdb) py-bt Python Exception Variable 'func' not found.: Error occurred in Python command: Variable 'func'

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

Jeremy Kloth added the comment: It seems that commit (https://github.com/python/cpython/commit/c52572319cbd50adff85050a54122c25239a516d) changed the parameter name in the definition of _PyCFunction_FastCallDict(). I believe that changing 'func_obj' to just 'func' should fix it (in Tools/gdb/

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

Mikhail added the comment: The actual stack, which I'm trying to debug, begins like this: #0 0xbfbfd34e in ?? () #1 0x2a9ec81e in ?? () from /opt/lib/qt5/libQt5WebKit.so.5 #2 0x2acf0efe in ?? () from /opt/lib/qt5/libQt5WebKit.so.5 #3 0x2acd8b74 in ?? () from /opt/lib/qt5/libQt5WebKit.so.5 #4

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

Mikhail added the comment: I rebuilt my python-3.6.1 with the path (https://github.com/python/cpython/commit/d05f7fdf6cf77724bd3064fb5a0846ef5cfe0c88) and tried debugging again -- same problem: % gdb7121 /opt/bin/python3.6 ... (gdb) r SCRIPT.py Thread 1 received signal SIGSEGV, Segmentation fa

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

STINNER Victor added the comment: New changeset d05f7fdf6cf77724bd3064fb5a0846ef5cfe0c88 by Victor Stinner in branch '3.6': [3.6] bpo-30345: Update test_gdb.py and python-gdb.py from master (#1549) https://github.com/python/cpython/commit/d05f7fdf6cf77724bd3064fb5a0846ef5cfe0c88 -- _

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

Charalampos Stratakis added the comment: So the issue wasn't restricted to a specific gdb version or distro release, as due to some issues dependency issues the gdb binary wasn't pulled in the buildroot which makes test_gdb to get skipped. So I was able to reproduce it on my system by installi

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

Charalampos Stratakis added the comment: Note: test_gdb is skipped on later Fedora's actually (possibly due to gdb package no being dragged at the minimal buildroot) so the issue might still be there, so the gdb version might have no effect on that. Will investigate further. -- _

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

STINNER Victor added the comment: I created https://github.com/python/cpython/pull/1549 to update test_gdb.py and python-gdb.py in Python 3.6. I don't know if it will fix the issus, but it shouldn't hurt :-) -- ___ Python tracker

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

Changes by STINNER Victor : -- pull_requests: +1647 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

Charalampos Stratakis added the comment: All the dependencies dragged. gdb is of version 7.11. The failures do not happen with gdb 7.12 (which exists in later Fedora releases). -- Added file: http://bugs.python.org/file46857/root.log ___ Python trac

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

Charalampos Stratakis added the comment: Full build log -- nosy: +cstratak Added file: http://bugs.python.org/file46856/build.log ___ Python tracker ___ _

[issue30345] test_gdb fails on Python 3.6 when built with LTO+PGO

New submission from STINNER Victor: cstratak reported the following test failure on Fedora 24 when building Python 3.6 with LTO + PGO: == FAIL: test_threads (test.test_gdb.PyBtTests) Verify that "py-bt" indicates threads that a