This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug corefiles/15810] gdb 7.3.1/7.5 unlinks and creates .pyc-files in non-user directories
- From: "kdevel at vogtner dot de" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Fri, 02 Aug 2013 14:40:28 +0000
- Subject: [Bug corefiles/15810] gdb 7.3.1/7.5 unlinks and creates .pyc-files in non-user directories
- Auto-submitted: auto-generated
- References: <bug-15810-4717 at http dot sourceware dot org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=15810
Stefan <kdevel at vogtner dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |---
--- Comment #2 from Stefan <kdevel at vogtner dot de> ---
(In reply to Tom Tromey from comment #1)
> These unlinks come from libpython, not gdb.
libpython is compiled/linked into gdb therefore these unlinks come from gdb.
> They are part of Python's byte-compilation approach.
And who has "bought" that?
> I don't think there is anything we can do about them.
You can to lots of different things only limited by your imagination:
1. You may warn the user who compiles gdb or the end user about this side
effects.
2. You can make --with-python=no the default.
3. You can remove the python support.
> So, I'm closing this.
Can you tell me a side effect in libpython which would be strong enough to
motivate you not to close this bug?
--
You are receiving this mail because:
You are on the CC list for the bug.