[Bug testsuite/30553] New: [gdb/testsuite] FAIL: gdb.base/sym-file.exp: continue to breakpoint: bar (the program exited)

[Bug testsuite/30553] New: [gdb/testsuite] FAIL: gdb.base/sym-file.exp: continue to breakpoint: bar (the program exited)

[vries at gcc dot gnu.org]

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

            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) != 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.

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