package.bbclass: add debug-without-src PACKAGE_DEBUG_SPLIT_STYLE
PATCH 1/1 package.bbclass: add debug-without-src PACKAGE_DEBUG_SPLIT_STYLE
* same as original and default version, but does not package source files in PN-dbg
--- meta/classes/package.bbclass | 6 ++++++ 1 file changed, 6 insertions(+)
meta/classes/package.bbclass +6 -0
@@ -682,6 +682,12 @@ python split_and_strip_files () { debugdir = "" debuglibdir = "/usr/lib/debug" debugsrcdir = "/usr/src/debug" + elif d.getVar('PACKAGE_DEBUG_SPLIT_STYLE', True) == 'debug-without-src': + # Original OE-core, a.k.a. ".debug", style debug info, but without sources in /usr/src/debug + debugappend = "" + debugdir = "/.debug" + debuglibdir = "" + debugsrcdir = "" else: # Original OE-core, a.k.a. ".debug", style debug info debugappend = ""
Signature · 1 line
1.8.1.5
Quoted 1 line · Martin Jansa
* same as original and default version, but does not package source files in PN-dbg
You can mark this as closing
https://bugzilla.yoctoproject.org/show_bug.cgi?id=3621, which would be good for my bug list. Richard had concerns that he listed in the bug, so having done tests and demonstrating that the loss of source doesn't impact the usefulness of the debug files would be good.
Ross
Quoted 8 lines · Ross
Quoted 1 line · Martin Jansa
* same as original and default version, but does not package source files in PN-dbg
You can mark this as closing
https://bugzilla.yoctoproject.org/show_bug.cgi?id=3621, which would be good for my bug list. Richard had concerns that he listed in the bug, so having done tests and demonstrating that the loss of source doesn't impact the usefulness of the debug files would be good.
I am curious as to the use of the dbg package (w/o) source on the target system.
In my experience, the dbg binaries are useless without the associated source. Most of the people I know either use an on-target debugger or a cross debugger, both of which need the associated sources to tell you anything about what is going on.
For someone who just wants pure backtrace information, it's usually easier to avoid the whole split-and-strip process that generates the dbg files. But of course this can sacrifice the usefulness of being able to do field debugging.
(Note, I'm not against the patch.. it looks fine to me... I just don't understand the usefulness.. other then the associated defect says they are "too big", which again, I don't doubt.)
--Mark
Quoted 7 lines
Ross
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Quoted 17 lines · Mark Hatle
Quoted 8 lines · Ross
Quoted 1 line · Martin Jansa
* same as original and default version, but does not package source files in PN-dbg
You can mark this as closing
https://bugzilla.yoctoproject.org/show_bug.cgi?id=3621, which would be good for my bug list. Richard had concerns that he listed in the bug, so having done tests and demonstrating that the loss of source doesn't impact the usefulness of the debug files would be good.I am curious as to the use of the dbg package (w/o) source on the target system.
In my experience, the dbg binaries are useless without the associated source. Most of the people I know either use an on-target debugger or a cross debugger, both of which need the associated sources to tell you anything about what is going on.
Quoted 7 lines
For someone who just wants pure backtrace information, it's usually easier to avoid the whole split-and-strip process that generates the dbg files. But of course this can sacrifice the usefulness of being able to do field debugging.
(Note, I'm not against the patch.. it looks fine to me... I just don't understand the usefulness.. other then the associated defect says they are "too big", which again, I don't doubt.)
I've added my use-case for this in bug report:
My use case was a bit different: to be able to build proprietary blobs with OE and exchange resulting .ipk files with partners without revealing source in PN-dbg.
So better backtrace is all we want from PN-dbg and devs with access to sources can download/checkout source on target (while using the same PN-dbg package to reproduce reported issue).
Signature · 1 line
Martin 'JaMa' Jansa jabber: [email protected]