From: "Monsees, Steven C (US)" <steven.monsees@baesystems.com>
To: Ross Burton <ross.burton@arm.com>
Cc: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: RE: [yocto] enabling symbols for debug in clinfo
Date: Mon, 9 May 2022 13:36:02 +0000 [thread overview]
Message-ID: <20220509133715.3C6DDC433F5@smtp.lore.kernel.org> (raw)
In-Reply-To: <C43FA290-46CE-41F9-84ED-BF78D35BA152@arm.com>
I will need to test but, that appears to have done the trick...
root@sbcb-default gdb clinfo
GNU gdb (GDB) 8.3.1
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-poky-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from clinfo...
Reading symbols from /usr/bin/.debug/clinfo...
(gdb)
Thanks
Steve
-----Original Message-----
From: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org> On Behalf Of Ross Burton
Sent: Monday, May 9, 2022 7:56 AM
To: Monsees, Steven C (US) <steven.monsees@baesystems.com>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] enabling symbols for debug in clinfo
External Email Alert
This email has been sent from an account outside of the BAE Systems network.
Please treat the email with caution, especially if you are requested to click on a link, decrypt/open an attachment, or enable macros. For further information on how to spot phishing, access “Cybersecurity OneSpace Page” and report phishing by clicking the button “Report Phishing” on the Outlook toolbar.
Unless clinfo is doing something wrong, it will be built with -g anyway. You’ll just need to install clinfo-dbg to get the symbols, as they’ll be split out into a separate package during packaging.
Ross
> On 9 May 2022, at 11:54, Monsees, Steven C (US) via lists.yoctoproject.org <steven.monsees=baesystems.com@lists.yoctoproject.org> wrote:
>
>
> Hello:
>
> I’d like to build clinfo w/ “-g” option to do some debugging with GDB…
>
> I am looking at:
> meta-openembedded/meta-oe/recipes-support/opencl/clinfo_2.2.18.04.06.b
> b
>
> I created a “bbapend” file to modify the build recipes “Makefile.am” file prior to build, to introduce ‘-g’ for CFLAGS & CPPFLAGS, i.e. at top of Makefile.am added:
>
> AM_CFLAGS - -g
> AM_CPPFLAGS = -g
>
> I checked the build tree and see my modified “Makefile.am” updated as expected, the update occurs at the end of the install process, using do_install_append… so the build should have used my modified file… but I do not have symbols for the clinfo package when I go to use GDB.
>
> Is there a simple way to enable debug symbols for this package ?
>
> Did I modify the wrong configuration file?, Should I be modifying configure ?
>
> I am new to auto-build configurations… Could someone tell me the
> easiest way to add “-g” to the clinfo standard build ?
>
> Thanks,
> Steve
>
>
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
prev parent reply other threads:[~2022-05-09 13:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MADEUP.16ED6A72C4624DE7.14253@lists.yoctoproject.org>
2022-05-09 11:04 ` [yocto] enabling symbols for debug in clinfo Quentin Schulz
2022-05-09 11:55 ` Ross Burton
2022-05-09 13:36 ` Monsees, Steven C (US) [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=20220509133715.3C6DDC433F5@smtp.lore.kernel.org \
--to=steven.monsees@baesystems.com \
--cc=ross.burton@arm.com \
--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 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.