public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "koteswararao18 at gmail dot com" <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 03:04:27 +0000 [thread overview] Message-ID: <bug-30784-4717-Gd1AqOoyyN@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30784-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30784 --- Comment #2 from nelakurthi koteswararao <koteswararao18 at gmail dot com> --- Dear Simon Marchi, >>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. Yes. i copied the built library "libshibsp-lite.so.10.0.3" to /lib64/libshibsp-lite.so.10 on target and launched gdb on application by setting breakpoints which is failing with error "Single stepping until exit from function..." as mentioned in my previous comment. regards koti -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-08-21 3:04 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 2023-08-21 3:04 ` koteswararao18 at gmail dot com [this message] 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-Gd1AqOoyyN@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).