We need to exercise IMAGE_GEN_DEBUGFS in oeselftest. Something like this will exercise all the backends for a non-trivial image: set IMAGE_GEN_DEBUGFS=1 for packageclass in rpm deb ipk: bitbake core-image-base
I guess we should also be checking that the generated tarball does in fact contain debug symbols that work, but that can be step 2.
Didn't made it to M1, moving to M2.
Patch sent http://lists.openembedded.org/pipermail/openembedded-core/2017-June/138398.html
Patch v2 sent http://lists.openembedded.org/pipermail/openembedded-core/2017-June/138519.html
Patch v3 sent http://lists.openembedded.org/pipermail/openembedded-core/2017-June/138893.html
This wasn't integrated on 2.4 M3. Moving the target to 2.5 M1.
Rebased and sent patch v4 http://lists.openembedded.org/pipermail/openembedded-core/2017-December/145415.html
patch send in comment 3,4 and 5 the changes are similar and the commit Id is same in all the three patches. This is expected ?
Consider the patches from comment 3 and comment 7, applied these patches to the latest 2.5.1 release and tested the test_image_gen_debugfs case and successfully passed.
Enhanced patch submitted. https://lists.openembedded.org/g/openembedded-core/topic/patch/72694485?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,72694485
Sent v02 patch https://lists.openembedded.org/g/openembedded-core/message/137697