Re: [patch] GDB 7.2: new feature for "backtrace" that cuts path to file (remain filename)

[Phil Muldoon <pmuldoon at redhat dot com>]

Joel Brobecker <brobecker@adacore.com> writes:

>> 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.

Yeah, agreed. Eventually my plan is to move all of the Python backtrace
code (as in the actual Python backtrace code written in Python) into GDB
'C' and implement call backs for a Python scripter to use.  But that
still won't solve the Python-on-X-platform issue.

> 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.

Good point.  I have no strong opinion either way.  I think this would be
a cool addition, though.

Cheers

Phil