From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id E7F7A3858C1F; Wed, 14 Jun 2023 14:45:22 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E7F7A3858C1F
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1686753922;
	bh=Hr8felI1NLFAyOadP+vS28PIC0Ol31vKd/ONbiOXFBY=;
	h=From:To:Subject:Date:From;
	b=ScqsR/BD3/r+g8a91t9Y/wmXb5NNvdV7mqM4AkvHHHxn6qUVyLI+UqGokJWA0mZQq
	 k2P6mbDphL4LlRwoL1kuvgMOeX47HGUnAJzhEbjVVVz008VRsmEbI4K+A/5bMvFFKU
	 eqCtD2sufL2kiucw/RkguOp8ZsXWs4loVycR/2QQ=
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/30553] New: [gdb/testsuite] FAIL:
 gdb.base/sym-file.exp: continue to breakpoint: bar (the program exited)
Date: Wed, 14 Jun 2023 14:45:22 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: NEW
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: bug_id short_desc product version bug_status
 bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-30553-4717@http.sourceware.org/bugzilla/>
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: <gdb-prs.sourceware.org>

https://sourceware.org/bugzilla/show_bug.cgi?id=3D30553

            Bug ID: 30553
           Summary: [gdb/testsuite] FAIL: gdb.base/sym-file.exp: continue
                    to breakpoint: bar (the program exited)
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: testsuite
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

On powerpc64-linux (CentOS 7), I run into:
...
(gdb) PASS: gdb.base/sym-file.exp: info files must display sym-file-lib
continue^M
Continuing.^M
[Inferior 1 (process 60062) exited with code 01]^M
(gdb) FAIL: gdb.base/sym-file.exp: continue to breakpoint: bar (the program
exited)
...

After some debugging, I found it's due to this returning:
...
 /* Call bar from SHLIB_NAME.  */
  if (lookup_function (lib, "bar", (void *) &pbar) !=3D 0)
    return 1;
...
rather than continuing and executing:
...
  (*pbar) ();
...
which would have triggered the breakpoint.

The test-case contains some dlsym implementation.

It could be already confused by bar being a D symbol in the .opd section,
rather than a T symbol in the .text section.

But AFAICT, the loaded symbol table contains garbage, so possibly it's a
little-endian only implementation.

It makes me wonder why dlsym is not used.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=