Bug 1657

Summary: debuginfo export
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Mark Hatle <mark.hatle>
Component: devtools / tool chainAssignee: Mark Hatle <mark.hatle>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: Low CC: bluelightning, jessica.zhang, meta.mr.watcher, meta.watcher, poky.bs.watcher, poky.watcher, richard.purdie
Version: unspecified   
Target Milestone: Future   
Hardware: All   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Yes (doc changes required)

Description Mark Hatle 2011-10-05 12:04:37 UTC 
Using the output of the filesystem generation (what packages ended up on the target), have a way to populate/export the corresponding debug information for use either on the target -- or on a host using cross-gdb.
Comment 1 Richard Purdie 2011-10-06 04:26:58 UTC 
For reference this does partially exist already - if you add dbg-pkgs to IMAGE_FEATURES you will have an image suitable for on target debugging with the debug info present.
Comment 2 Mark Hatle 2011-10-06 07:43:10 UTC 
The two usage scenarios that are different from existing behavior:

1) Target does not have enough space [or there is a desire to NOT have debuginfo on the target]
 -- this enables cross-gdb debugging

2) Target image being produced is a "production" image, and the device manufacturer wants a tarball of the corresponding debuginfo files for field debugging "as necessary".
Comment 3 Mark Hatle 2016-06-08 18:56:37 UTC 
This was implemented in YP 2.1.