Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] package.bbclass: add debug-without-src PACKAGE_DEBUG_SPLIT_STYLE
Date: Wed, 13 Mar 2013 15:08:34 +0100	[thread overview]
Message-ID: <20130313140834.GJ3260@jama> (raw)
In-Reply-To: <513F4BF9.4090903@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 1873 bytes --]

On Tue, Mar 12, 2013 at 10:38:33AM -0500, Mark Hatle wrote:
> On 3/12/13 10:28 AM, Burton, Ross wrote:
> > On 12 March 2013 04:24, Martin Jansa <martin.jansa@gmail.com> wrote:
> >> * 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.)

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).

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

      reply	other threads:[~2013-03-13 14:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12 11:24 [PATCH] package.bbclass: add debug-without-src PACKAGE_DEBUG_SPLIT_STYLE Martin Jansa
2013-03-12 15:28 ` Burton, Ross
2013-03-12 15:38   ` Mark Hatle
2013-03-13 14:08     ` Martin Jansa [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130313140834.GJ3260@jama \
    --to=martin.jansa@gmail.com \
    --cc=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox