relative path in -dbg packages

[Mathieu Malaterre <malat@debian.org>]

While reading the wiki page for AutomaticDebugPackages, I was
wondering if it is possible to post-processed object file to
manipulate relatives path for debug info ?

Typical use case is that after installing the -dbg package, you end up
with a gdb backtrace saying:

[...]
brw_meta_fast_clear (brw=brw@entry=0x7fffd4097a08,
fb=fb@entry=0x7fffd40fa900, buffers=buffers@entry=2,
partial_clear=partial_clear@entry=false)
    at ../../../../../../../src/mesa/drivers/dri/i965/brw_meta_fast_clear.c:447
447 ../../../../../../../src/mesa/drivers/dri/i965/brw_meta_fast_clear.c:
No such file or directory.
[...]

Unless you create a fake directory tree, it is tedious to get any
sense of the above.

Sometimes you even get a hardcoded "/buildd" toplevel path, which may
be annoying to create just to get proper context (function name,
instruction...) for reporting a bug.

So my questions are:
1. Is it possible to post-processed those objects file and change
relative path to full path
2. Is it possible to reserve a system path for debug information, eg
all debug paths should start with "/usr/src/debug"

Thanks for comments,