public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug c++/30784] Single stepping until exit from function _ZN6shibsp8SPConfig4initEPKcS2_@plt, which has no line number information Date: Mon, 21 Aug 2023 01:44:42 +0000 [thread overview] Message-ID: <bug-30784-4717-OiyRfLx9rv@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30784-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30784 Simon Marchi <simark at simark dot ca> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |simark at simark dot ca --- Comment #1 from Simon Marchi <simark at simark dot ca> --- Just a guess: because of the ".libs" directory, it sounds like the application you debug uses libtool as part of its build system. If so, if you want to debug the application, running it inside the build tree, you need to use the libtool wrapper: $ libtool --mode execute gdb your-binary libtool will set up the appropriate LD_LIBRARY_PATH and other variables so that your program will pick up the libraries How do you run gdb in your case? The message that says "/lib64/libshibsp-lite.so.10" is a sign that your application is picking up the library installed on the system, not the library in your build tree. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-08-21 1:44 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-20 16:11 [Bug c++/30784] New: " koteswararao18 at gmail dot com 2023-08-20 16:13 ` [Bug c++/30784] " koteswararao18 at gmail dot com 2023-08-21 1:44 ` simark at simark dot ca [this message] 2023-08-21 3:04 ` koteswararao18 at gmail dot com 2023-08-21 19:35 ` tromey at sourceware dot org 2023-08-21 19:41 ` simark at simark dot ca 2023-08-22 14:16 ` koteswararao18 at gmail dot com 2023-08-22 15:08 ` simark at simark dot ca
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=bug-30784-4717-OiyRfLx9rv@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).