Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Pascal Bach <pascal.bach@siemens.com>
To: "Andreas Müller" <schnitzeltony@googlemail.com>,
	"Richard Purdie" <richard.purdie@linuxfoundation.org>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: Debugging using sysroots and GDB
Date: Tue, 8 Mar 2016 15:06:19 +0100	[thread overview]
Message-ID: <56DEDC5B.4050501@siemens.com> (raw)
In-Reply-To: <CALbNGRQbfu45fM=kijvTnx4sY2SzjiVSCtGXhyt0xM+akP1sSQ@mail.gmail.com>

Hi Andreas
> I am using sysroot for debugging too. I have no
>
> * INHERIT += "rm_work"
>
> and added
>
> INHIBIT_SYSROOT_STRIP = "1"
>
> to my local.conf
>
> I use this approach for very long time now and from my point of view
> it has one BIG advantage: I can use these settings for productive
> images and start remote debug within seconds without further
> rebuilding.
> OK - default compiler optimization sometimes causes headaches but it
> works for solving >80% of my cases. In case I want to debug software
> that I have developed setting optimization recipe wise helps or I
> debug that on PC or target itself.
How do you deal with the case where there is no source in your work dir because the package was taken from sstate?
The only solution I found so far is to build without sstate :(

Pascal


  parent reply	other threads:[~2016-03-08 14:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-23 14:09 Debugging using sysroots and GDB Pascal Bach
2016-03-04  8:42 ` Pascal Bach
2016-03-04 11:20 ` Richard Purdie
2016-03-04 14:06   ` Pascal Bach
2016-03-04 15:30     ` Richard Purdie
2016-03-08  8:53       ` Pascal Bach
2016-03-08 11:22         ` Khem Raj
2016-03-08 14:09           ` Pascal Bach
2016-03-08 10:01   ` Andreas Müller
2016-03-08 10:24     ` Burton, Ross
2016-03-08 14:06     ` Pascal Bach [this message]
2016-03-08 19:57       ` Andreas Müller

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=56DEDC5B.4050501@siemens.com \
    --to=pascal.bach@siemens.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=schnitzeltony@googlemail.com \
    /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