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.
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.
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".
This was implemented in YP 2.1.