diff options
| author | Juergen Borleis <jbe@pengutronix.de> | 2017-06-14 17:08:59 +0200 |
|---|---|---|
| committer | Michael Olbrich <m.olbrich@pengutronix.de> | 2017-06-21 09:34:50 +0200 |
| commit | 56b1e28fdbf7873ccfc46fa82cef9734691a31e7 (patch) | |
| tree | 06caf0a337de44eb85dd668639d70f1722baa29f /rules/barebox.make | |
| parent | e6533aa2d924dcd302ff49b5b71d8ac1ea3876e7 (diff) | |
| download | ptxdist-56b1e28fdbf7873ccfc46fa82cef9734691a31e7.tar.gz ptxdist-56b1e28fdbf7873ccfc46fa82cef9734691a31e7.tar.xz | |
Debugging: add support for 'build-id's
Recent debugging tools support separate binaries and debug information
files. Providing a unique 'build-id' embedded in the binary enables the
debugging tools to select the correct and matching debug information
files from the system's root filesystem.
The 'build-id' is a 40 character calculated SHA1 from important sections in
the binary. The debug information files get stored at a central direcory at
"/usr/lib/debug/", with a special path based on the 'build-id'. If the
'build-id' is "123456789abcdef", the path and filename will be
".build-id/12/3456789abcdef.debug".
Its possible to have more than one 'build-id' in the binary. This
implementation prefers the first one in the list, which might be the
wrong one. It's unclear yet how the common debugging tools will behave in
this case.
Signed-off-by: Juergen Borleis <jbe@pengutronix.de>
Diffstat (limited to 'rules/barebox.make')
| -rw-r--r-- | rules/barebox.make | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/rules/barebox.make b/rules/barebox.make index 74576ce48..bdfefe8c6 100644 --- a/rules/barebox.make +++ b/rules/barebox.make @@ -37,7 +37,8 @@ BAREBOX_WRAPPER_BLACKLIST := \ TARGET_HARDEN_RELRO \ TARGET_HARDEN_BINDNOW \ TARGET_HARDEN_PIE \ - TARGET_DEBUG + TARGET_DEBUG \ + TARGET_BUILD_ID BAREBOX_ENV := \ KCONFIG_NOTIMESTAMP=1 \ |