All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pascal Bach <pascal.bach@siemens.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: Debugging using sysroots and GDB
Date: Tue, 8 Mar 2016 09:53:53 +0100	[thread overview]
Message-ID: <56DE9321.4030404@siemens.com> (raw)
In-Reply-To: <1457105433.2804.30.camel@linuxfoundation.org>

Hi Richard
> Using this method is a supported approach. I'm a little surprised
> .debug directories don't work. Have you tried just setting:
>
> set sysroot /home/projects/rootfs-dbg
> set substitute-path /usr/src/debug /home/projects/rootfs
> -bbg/usr/src/debug
This doesn't seem to work (tried only with dizzy).
The only way I could get this to work is to extract both the rootfs and the rootfs-dbg into the same place and then set sysroot to that location.
Is this the way it is supposed to be?

>
> as I believe it should work with IMAGE_GEN_DEBUGFS=1 "out the box". If
> it doesn't that is a bug and we should try and look into fixing that.
I'm currently using dizzy. I will give it another try with jethro next week maybe it is working there.

Pascal


  reply	other threads:[~2016-03-08  8:53 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 [this message]
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
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=56DE9321.4030404@siemens.com \
    --to=pascal.bach@siemens.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.