1657 2011-10-05 12:04:37 +0000 debuginfo export 2016-06-08 18:56:37 +0000 1 1 7 Build System, Metadata & Runtime OE-Core devtools / tool chain unspecified All Multiple RESOLVED FIXED Low enhancement Future 1 mark.hatle mark.hatle bluelightning jessica.zhang meta.mr.watcher meta.watcher poky.bs.watcher poky.watcher richard.purdie --- --- Yes (doc changes required) oldest_to_newest 16731 0 mark.hatle 2011-10-05 12:04:37 +0000 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. 16737 1 richard.purdie 2011-10-06 04:26:58 +0000 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. 16741 2 mark.hatle 2011-10-06 07:43:10 +0000 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". 62787 3 mark.hatle 2016-06-08 18:56:37 +0000 This was implemented in YP 2.1.