From: Simon Marchi via lttng-dev <lttng-dev@lists.lttng.org>
To: "Seidl, Aron" <aron.seidl@zeiss.com>,
"lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] Debugging Libaries in Babeltrace 2
Date: Wed, 25 Oct 2023 11:31:07 -0400 [thread overview]
Message-ID: <d3c4203d-009f-422a-b75e-8c5c7fb9fa84@simark.ca> (raw)
In-Reply-To: <AM9P190MB1075EE7CA033D45006FCDB0D88DEA@AM9P190MB1075.EURP190.PROD.OUTLOOK.COM>
On 10/25/23 03:29, Seidl, Aron via lttng-dev wrote:
> Hi Simon,
> Thanks for your quick answer!
> I run GDB like this:
> gdb --args ./babeltrace2 /home/aron/Schreibtisch/kernel4 -o text
> (I'm in src/cli/.libs)
Don't do that (try to debug the binary in .libs directly).
> I don't think I've ever installed a System Version of babeltrace2, so it is really weird that GDB uses following library:
>
> 0x00007ffff7f36f00 0x00007ffff7f89749 Yes (*) /lib/x86_64-linux-gnu/libbabeltrace2.so.0
> (*): Shared library is missing debugging information.
It might have been installed as a dependency of another package, I don't
know.
> And you're absolutely right! That is the reason why I can't debug it.
> Is there a way to specify the library path? Because even with the libtool wrapper, GDB uses the release version of libbabeltrace2.so.0.
Can you run this *in the root of your build tree* and show the output?
We should see a path to libbabeltrace2.so inside your build tree.
$ libtool --mode=execute gdb -q -batch src/cli/babeltrace2 -ex start -ex "info shared"
Simon
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
prev parent reply other threads:[~2023-10-25 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 15:52 Seidl, Aron via lttng-dev
2023-10-24 18:51 ` Simon Marchi via lttng-dev
2023-10-25 7:29 ` Seidl, Aron via lttng-dev
2023-10-25 14:50 ` Philippe Proulx via lttng-dev
2023-10-26 10:21 ` Seidl, Aron via lttng-dev
2023-10-25 15:31 ` Simon Marchi via lttng-dev [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=d3c4203d-009f-422a-b75e-8c5c7fb9fa84@simark.ca \
--to=lttng-dev@lists.lttng.org \
--cc=aron.seidl@zeiss.com \
--cc=simark@simark.ca \
/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