This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] GDB 7.2: new feature for "backtrace" that cuts path to file (remain filename)
- From: Daniel Jacobowitz <drow at false dot org>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: Phil Muldoon <pmuldoon at redhat dot com>, iam ahal <hal9000ed2k at gmail dot com>, gdb-patches at sourceware dot org
- Date: Sun, 3 Jul 2011 14:12:09 -0400
- Subject: Re: [patch] GDB 7.2: new feature for "backtrace" that cuts path to file (remain filename)
- References: <BANLkTinD+9_Mkug8o2VhZ03L6XSriL_RKQ@mail.gmail.com> <m3oc1kfheh.fsf@redhat.com> <20110627160029.GF20676@adacore.com>
On Mon, Jun 27, 2011 at 09:00:29AM -0700, Joel Brobecker wrote:
> Yeah, I am wondering which way would be best. It seems like a Python
> backtrace decorator would already work, or could be made to work.
> But on the other hand, we can't ignore the fact that linking against
> the Python library is not necessary easy. In particular, things seems
> to work OK on Windows, but I noticed that GDB crashes when trying to
> source a Python script. I haven't tried linking with Python on x64
> Windows yet.
FYI, when you get this symptom, it probably means (used to mean?) that
the Python library is linked to a different version of the MSVC
runtime than GDB is.
I think someone posted a patch to work around this issue by not
passing a FILE* to Python. Then again, my memory's not so good... I
thought it was you... :-)
--
Daniel Jacobowitz