From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D7113385770F; Mon, 21 Aug 2023 01:44:43 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D7113385770F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1692582283; bh=3SgmrKIfpSGIGVGYKzsQJlXhCSlKUdL+BNqO8je/984=; h=From:To:Subject:Date:In-Reply-To:References:From; b=yU6JxbrcsFa2fgNyK34ERLWXTYtnm3vxqQpQaLmElNnkMMa+GnOP4TkAcPs9Wf6Lp hK4uYR0NOvclTIo6wz6+yfrMc+Rfip2S06crMnkQnXVP+csJHY4AUrVh4HWYo6deFB gl/joMG5fuMiEdOdc5yEedlApVWJmg5PSNr9wAE0= From: "simark at simark dot ca" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: c++ X-Bugzilla-Version: 12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: simark at simark dot ca X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30784 Simon Marchi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |simark at simark dot ca --- Comment #1 from Simon Marchi --- Just a guess: because of the ".libs" directory, it sounds like the applicat= ion 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 libr= ary in your build tree. --=20 You are receiving this mail because: You are on the CC list for the bug.=