[Bug 1095499] New: Let's come up with python3-debug package
http://bugzilla.opensuse.org/show_bug.cgi?id=1095499 Bug ID: 1095499 Summary: Let's come up with python3-debug package Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: martin.liska@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- In order to support debugging experience, it's needed to build python without optimizations. Fedora has a python3-debug package. I would do the same: https://src.fedoraproject.org/rpms/python3/blob/master/f/python3.spec#_596 Note that it will fix: https://bugs.python.org/issue30345 and similar issues. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1095499
http://bugzilla.opensuse.org/show_bug.cgi?id=1095499#c1
Martin Liška
http://bugzilla.opensuse.org/show_bug.cgi?id=1095499
http://bugzilla.opensuse.org/show_bug.cgi?id=1095499#c2
--- Comment #2 from Matej Cepl
http://bugzilla.opensuse.org/show_bug.cgi?id=1095499
http://bugzilla.opensuse.org/show_bug.cgi?id=1095499#c3
--- Comment #3 from Martin Liška
I am not sure how really necessary it is, I had pretty reasonable experience debugging with (not of) python binary as it is.
Yes, it worked fine for me I would say. But as enabled -flto it broke debugging experience completely.
If you develop CPython itself, then you probably work out of the git checkout anyway, don't you?
However, if you want to make a subpackage for python{,3}-base or something, then show me some OBS repo to investigate.
There's devel project: https://build.opensuse.org/package/show/devel:languages:python:Factory/pytho... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1095499
http://bugzilla.opensuse.org/show_bug.cgi?id=1095499#c4
--- Comment #4 from Matej Cepl
Yes, it worked fine for me I would say. But as enabled -flto it broke debugging experience completely.
Isn't it just a question of gdb catching up? Or perhaps bug in the SUSE build of gdb? Do you know?
There's devel project: https://build.opensuse.org/package/show/devel:languages:python:Factory/ python3
Of course, I know about that, I meant, “Show me the code!”, a repo with suggested changes in it. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1095499
http://bugzilla.opensuse.org/show_bug.cgi?id=1095499#c5
--- Comment #5 from Martin Liška
(In reply to Martin Liška from comment #3)
Yes, it worked fine for me I would say. But as enabled -flto it broke debugging experience completely.
Isn't it just a question of gdb catching up? Or perhaps bug in the SUSE build of gdb? Do you know?
No, issue is that py-* commands rely on stack layout how python objects are passed. It's done then in: Tools/gdb/libpython.py.
There's devel project: https://build.opensuse.org/package/show/devel:languages:python:Factory/ python3
Of course, I know about that, I meant, “Show me the code!”, a repo with suggested changes in it.
It's simple, they have a configure option: %if %{with debug_build} BuildPython debug \ "--without-ensurepip --with-pydebug" \ "-O0" %endif # with debug_build Take a look at the Fedora spec file I linked in the first comment. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1095499
Matej Cepl
http://bugzilla.opensuse.org/show_bug.cgi?id=1095499
Petr Gajdos
http://bugzilla.opensuse.org/show_bug.cgi?id=1095499
http://bugzilla.opensuse.org/show_bug.cgi?id=1095499#c6
--- Comment #6 from Matej Cepl
It's simple, they have a configure option:
%if %{with debug_build} BuildPython debug \ "--without-ensurepip --with-pydebug" \ "-O0" %endif # with debug_build
No, it is not simple. We don't have multiple builds in separate subdirectories, we don't have BuildPython macro. If you want this functionality, complete patch with suggested changes (tested to work) would be welcome. We are now in the process of upgrading to 3.7.0 so this is the time for radical changes. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com