[Bug 1169468] devel:gcc/gdb: Bug gdb errors when exec'd from 'other' pyenv
http://bugzilla.suse.com/show_bug.cgi?id=1169468 http://bugzilla.suse.com/show_bug.cgi?id=1169468#c3 --- Comment #3 from Michael Matz <matz@suse.com> --- (In reply to Richard Biener from comment #2)
That would also need a more explicit dependency on python though, no?
% ldd /usr/bin/gdb ... libpython3.7m.so.1.0 => /usr/lib64/libpython3.7m.so.1.0 (0x00007efc357de000) ... It already _has_ very explicit dependencies on python, so this would just clarify that. But I'm wondering if this change alone helps with pyenv?
Not sure if we should care at all - is pyenv some "supported" feature? I suspect many packages fall foul of its behavior.
Yeah, but if we can robustify gdb somewhat that's appreciated. Of course, if pyenv uses too forceful means to override the system python at runtime, then all bets are off (and indeed, other system packages requiring python will probably break in similarly mysterious ways). -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com