yocto.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
From: bohdan.shubenok@sigma.software
To: yocto@lists.yoctoproject.org
Subject: Re: #dunfell Path to sources in debugfs
Date: Wed, 06 Oct 2021 00:32:45 -0700	[thread overview]
Message-ID: <16836.1633505565229500112@lists.yoctoproject.org> (raw)
In-Reply-To: <a1ce9afc-d5e3-0065-325b-b85a296cb2ff@gmail.com>

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

Hi,

I`m trying to debug without connection to target at all. This are the examples of what I`m running:

# gdb-multiarch b2010_rootfs/usr/bin/noah-heatsystem var/volatile/crash/core.noah.565
(gdb) set sysroot b2010_rootfs/
(gdb) set substitute-path /usr/src/debug b2010/usr/src/debug
.... things are getting loaded .....

(gdb) bt
#0  0xb4a6a144 in saveCursorsOnList (p=0xccf34862, iRoot=3, pExcept=0xb540b350) at ../sqlite-autoconf-3310100/sqlite3.c:64883
.... more frames here .....

And this how it looks like when out of tree build disabled:

# gdb-multiarch b2010_rootfs/usr/bin/noah-heatsystem var/volatile/crash/core.noah.565
(gdb) set sysroot src_add_rootfs/
(gdb) set substitute-path /usr/src/debug src_add_rootfs/usr/src/debug
.... things are getting loaded .....

(gdb) bt
#0  0xb4a6a144 in saveCursorsOnList (p=0xccf34862, iRoot=3, pExcept=0xb540b350) at sqlite3.c:64883
.... more frames here .....

In a  first case `layout next` command shows that no source code can be found and in a second case source code is shown.

Best regards,

Bohdan.

[-- Attachment #2: Type: text/html, Size: 1226 bytes --]

       reply	other threads:[~2021-10-06  7:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a1ce9afc-d5e3-0065-325b-b85a296cb2ff@gmail.com>
2021-10-06  7:32 ` bohdan.shubenok [this message]
     [not found] <b0446ec1-7601-b97e-567e-4cfd88c3581c@gmail.com>
2021-10-06  6:18 ` #dunfell Path to sources in debugfs bohdan.shubenok
2021-10-05 14:04 bohdan.shubenok

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=16836.1633505565229500112@lists.yoctoproject.org \
    --to=bohdan.shubenok@sigma.software \
    --cc=yocto@lists.yoctoproject.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;
as well as URLs for NNTP newsgroup(s).