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: Joel Brobecker <brobecker at adacore dot com>
- To: Phil Muldoon <pmuldoon at redhat dot com>
- Cc: iam ahal <hal9000ed2k at gmail dot com>, gdb-patches at sourceware dot org
- Date: Mon, 27 Jun 2011 09:00:29 -0700
- 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>
> You could use Python to write a custom backtrace to do this. But that
> is neither here or there to this patch.
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.
So, there are pluses and minuses on both ends. I am wondering
what everyone else thinks...
If we were to implement this in GDB itself, I'd rather go with
a setting rather than a command-line option. But that's just
a suggestion.
--
Joel