This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug python/18730] New: verify correct __init__.py is being loaded
- From: "dje at google dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 28 Jul 2015 23:31:58 +0000
- Subject: [Bug python/18730] New: verify correct __init__.py is being loaded
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=18730
Bug ID: 18730
Summary: verify correct __init__.py is being loaded
Product: gdb
Version: unknown
Status: NEW
Severity: normal
Priority: P2
Component: python
Assignee: unassigned at sourceware dot org
Reporter: dje at google dot com
Target Milestone: ---
If one happens to start a gdb from a build tree, or a staging area (e.g., make
install DESTDIR=/build/gdb/staging), and there's some installation error, gdb
may end up using /usr/share/gdb/python/gdb/__init__py (or whatever the
configured data dir is). There's no guarantee that the currently installed
__init__.py is compatible with the gdb being run.
Either gdb needs to not fallback to using the configured data-dir if it can't
find data-dir relative to its current location
(e.g., /build/gdb/staging/usr/bin/gdb -> /build/gdb/staging/usr/share/gdb, or
whatever),
or we should at least verify that the data-dir we find is for the same version
of gdb.
--
You are receiving this mail because:
You are on the CC list for the bug.