For reference.
On Fri, Nov 14, 2014 at 2:34 PM, Mathieu Malaterre wrote:
> 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 -d
Mathieu Malaterre:
> 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 ?
As part of the reproducible builds effort [1], it has so far proven to
be very difficult to do so in a cons
* Neil Williams , 2014-11-14, 15:21:
Mathieu Malaterre wrote:
[...]
Sometimes you even get a hardcoded "/buildd" toplevel path,
Or /tmp/buildd/, or /home/bob/, which both smell like a (small) security
hole.
So my questions are:
1. Is it possible to post-processed those objects file and c
On Fri, 14 Nov 2014 14:34:19 +0100
Mathieu Malaterre wrote:
> 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,
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=
5 matches
Mail list logo
