From: James Feist <james.feist@linux.intel.com>
To: John Chung <gorojohn17@gmail.com>, openbmc@lists.ozlabs.org
Subject: Re: OpenBMC Source-Level Debugging
Date: Fri, 17 Jan 2020 13:54:47 -0800 [thread overview]
Message-ID: <0f56ce8a-a440-dbe8-b9ce-157c6f6185ee@linux.intel.com> (raw)
In-Reply-To: <CA+a15-UkHByO=6psLogPLpoPkaRCpCwVer_sswudwcm_nTBvjQ@mail.gmail.com>
On 1/14/20 5:02 AM, John Chung wrote:
> Hi All,
>
> I am doing a personal study on OpenBMC recently. And I am wondering that
> how to do source-level debugging via gdb, especially in vscode (Not sure
> it is possible or not).
This is how I get gdb running, there may be (probably are) better ways:
1. Add IMAGE_INSTALL_append += "gdb" to the end of your local.conf to
get gdb in the image.
2. devtool modify 'package' to modify package
3. scp
build/workspace/sources/<package-name>/oe-workdir/packages-split/<package-name>-dbg/usr/bin/.debug/<application-name>
onto image to get symbols.
4. gdb pacakge
5. symbol-file <file you just scpd>
Not sure about vscode usage.
-James
>
> If anyone has any experience or documentation, please kindly let me know.
>
> Very appreciated for the help.
>
> Thanks,
> John
>
>
next prev parent reply other threads:[~2020-01-17 21:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 13:02 OpenBMC Source-Level Debugging John Chung
2020-01-17 21:54 ` James Feist [this message]
2020-01-17 22:04 ` Bills, Jason M
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=0f56ce8a-a440-dbe8-b9ce-157c6f6185ee@linux.intel.com \
--to=james.feist@linux.intel.com \
--cc=gorojohn17@gmail.com \
--cc=openbmc@lists.ozlabs.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.