Re: [OE-core] how to configure an image with *full* debugging info in the libs and binaries?
Quoting Andre McCurdy : On Mon, Jul 19, 2021 at 5:06 PM Ross Burton wrote: On Fri, 16 Jul 2021 at 20:10, Robert P. J. Day wrote: > colleague just asked me what it would take to generate an image > where the executables and libraries contain all the gdb-related > debugging info in the same files (that is, not broken out in the > .debug directories). > > i pointed out that this would increase the size of the installable > target image substantially but, apparently, that is of no concern. This is where I have to ask "why?". All known debugging tools can handle split-out debuginfo, and getting them all installed into an image is as simple as IMAGE_FEATURES += dbg-pkgs, as Khem says. Why is an interesting side discussion. Getting back to the original question though, either OE officially supports creating unstripped binaries or it doesn't. The documentation should perhaps be updated to make that clear (and if there's legacy support for creating unstripped binaries still lurking in the code but we don't want anyone to use it, then maybe it should be removed...). It *appears* the combination of: INHIBIT_PACKAGE_STRIP = '1' INHIBIT_PACKAGE_DEBUG_SPLIT = '1' does what I want (at least at first glance). As to "why", I have been told there is a build/test infrastructure in place that works with just this format, and they would like to just keep doing that. And, frankly, that's a perfectly good reason. rday -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#154010): https://lists.openembedded.org/g/openembedded-core/message/154010 Mute This Topic: https://lists.openembedded.org/mt/84256404/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] how to configure an image with *full* debugging info in the libs and binaries?
On Mon, Jul 19, 2021 at 5:06 PM Ross Burton wrote: > On Fri, 16 Jul 2021 at 20:10, Robert P. J. Day wrote: > > colleague just asked me what it would take to generate an image > > where the executables and libraries contain all the gdb-related > > debugging info in the same files (that is, not broken out in the > > .debug directories). > > > > i pointed out that this would increase the size of the installable > > target image substantially but, apparently, that is of no concern. > > This is where I have to ask "why?". All known debugging tools can > handle split-out debuginfo, and getting them all installed into an > image is as simple as IMAGE_FEATURES += dbg-pkgs, as Khem says. Why is an interesting side discussion. Getting back to the original question though, either OE officially supports creating unstripped binaries or it doesn't. The documentation should perhaps be updated to make that clear (and if there's legacy support for creating unstripped binaries still lurking in the code but we don't want anyone to use it, then maybe it should be removed...). -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#154009): https://lists.openembedded.org/g/openembedded-core/message/154009 Mute This Topic: https://lists.openembedded.org/mt/84256404/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] how to configure an image with *full* debugging info in the libs and binaries?
On Fri, 16 Jul 2021 at 20:10, Robert P. J. Day wrote: > colleague just asked me what it would take to generate an image > where the executables and libraries contain all the gdb-related > debugging info in the same files (that is, not broken out in the > .debug directories). > > i pointed out that this would increase the size of the installable > target image substantially but, apparently, that is of no concern. This is where I have to ask "why?". All known debugging tools can handle split-out debuginfo, and getting them all installed into an image is as simple as IMAGE_FEATURES += dbg-pkgs, as Khem says. Ross -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#153999): https://lists.openembedded.org/g/openembedded-core/message/153999 Mute This Topic: https://lists.openembedded.org/mt/84256404/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] how to configure an image with *full* debugging info in the libs and binaries?
On Fri, 16 Jul 2021, Khem Raj wrote: > On Fri, Jul 16, 2021 at 12:10 PM Robert P. J. Day > wrote: > > > > > > colleague just asked me what it would take to generate an image > > where the executables and libraries contain all the gdb-related > > debugging info in the same files (that is, not broken out in the > > .debug directories). > > > > i pointed out that this would increase the size of the installable > > target image substantially but, apparently, that is of no concern. > > > > said colleague pointed me here as to what they were perusing: > > > > https://developer.ridgerun.com/wiki/index.php?title=Preparing_Yocto_Development_Environment_for_Debugging > > > > so, once i finish this current task, i'm going to take a shot at > > testing whether the following would do it: > > > > # Specifies to build packages with debugging information > > DEBUG_BUILD = "1" > > # Do not remove debug symbols > > INHIBIT_PACKAGE_STRIP = "1" > > # OPTIONAL: Do not split debug symbols in a separate file > > INHIBIT_PACKAGE_DEBUG_SPLIT= "1" > > > > am i on the right track? this seems straightforward enough, i'll just > > have to confirm those variables still exist, and that they do what i > > want. > > > > thoughts? is this as simple as i think it should be? > > I think you should try > > EXTRA_IMAGE_FEATURES_append = " tools-debug dbg-pkgs" pretty sure you don't need both "EXTRA_" and "_append". :-) > this should get you all needed debug info and tools on target > > then if you want to make optimization levels to favor debug info > generation set DEBUG_BUILD = "1" i'm ... not convinced (i'll be trying this later), but to be clear, i don't want separate .debug content, i want a single image with all the debug info right in the binaries and executables. i'll try some things later and we'll see what happens. rday -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#153946): https://lists.openembedded.org/g/openembedded-core/message/153946 Mute This Topic: https://lists.openembedded.org/mt/84256404/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] how to configure an image with *full* debugging info in the libs and binaries?
On Fri, Jul 16, 2021 at 12:10 PM Robert P. J. Day wrote: > > > colleague just asked me what it would take to generate an image > where the executables and libraries contain all the gdb-related > debugging info in the same files (that is, not broken out in the > .debug directories). > > i pointed out that this would increase the size of the installable > target image substantially but, apparently, that is of no concern. > > said colleague pointed me here as to what they were perusing: > > https://developer.ridgerun.com/wiki/index.php?title=Preparing_Yocto_Development_Environment_for_Debugging > > so, once i finish this current task, i'm going to take a shot at > testing whether the following would do it: > > # Specifies to build packages with debugging information > DEBUG_BUILD = "1" > # Do not remove debug symbols > INHIBIT_PACKAGE_STRIP = "1" > # OPTIONAL: Do not split debug symbols in a separate file > INHIBIT_PACKAGE_DEBUG_SPLIT= "1" > > am i on the right track? this seems straightforward enough, i'll just > have to confirm those variables still exist, and that they do what i > want. > > thoughts? is this as simple as i think it should be? I think you should try EXTRA_IMAGE_FEATURES_append = " tools-debug dbg-pkgs" this should get you all needed debug info and tools on target then if you want to make optimization levels to favor debug info generation set DEBUG_BUILD = "1" > > rday > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#153945): https://lists.openembedded.org/g/openembedded-core/message/153945 Mute This Topic: https://lists.openembedded.org/mt/84256404/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] how to configure an image with *full* debugging info in the libs and binaries?
colleague just asked me what it would take to generate an image where the executables and libraries contain all the gdb-related debugging info in the same files (that is, not broken out in the .debug directories). i pointed out that this would increase the size of the installable target image substantially but, apparently, that is of no concern. said colleague pointed me here as to what they were perusing: https://developer.ridgerun.com/wiki/index.php?title=Preparing_Yocto_Development_Environment_for_Debugging so, once i finish this current task, i'm going to take a shot at testing whether the following would do it: # Specifies to build packages with debugging information DEBUG_BUILD = "1" # Do not remove debug symbols INHIBIT_PACKAGE_STRIP = "1" # OPTIONAL: Do not split debug symbols in a separate file INHIBIT_PACKAGE_DEBUG_SPLIT= "1" am i on the right track? this seems straightforward enough, i'll just have to confirm those variables still exist, and that they do what i want. thoughts? is this as simple as i think it should be? rday -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#153944): https://lists.openembedded.org/g/openembedded-core/message/153944 Mute This Topic: https://lists.openembedded.org/mt/84256404/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
