This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

tui/2553: directory / path munging capability


>Number:         2553
>Category:       tui
>Synopsis:       directory / path munging capability
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Wed Nov 12 17:18:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     andreas@nodreams.com
>Release:        5.4.0 and 6.8
>Organization:
>Environment:
Any / all
>Description:
I have a program compiled on another host with the source tree in a different top-level path so gdb is unable to find the source files.  Adding all the 2600 directories to dir would be tedious.  Although CR 1215 would go a long way in rectifying this it would be nice if I could do something like:
if /build/src/wibble is the source directory on the machine that compiled the program and /mount/src/wibble is equivalent on the debugger machine, then when gdb fails to find /build/src/wibble/foo.c and I tell it to look in /mount/src/wibble for it, it will also magically find /mount/src/wobble/bar.c which was originally in /build/src/wobble/bar.c

please?
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]