Bug 24687 - FAIL: gdb.base/fullname.exp: set breakpoint by full path before/after loading symbols - built relative
Summary: FAIL: gdb.base/fullname.exp: set breakpoint by full path before/after loading...
Status: NEW
Alias: None
Product: gdb
Classification: Unclassified
Component: breakpoints (show other bugs)
Version: HEAD
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-16 22:33 UTC by Tom de Vries
Modified: 2019-10-15 15:18 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tom de Vries 2019-06-16 22:33:42 UTC
This FAILs start at "Only compute realpath when basenames_may_differ is set":
...
FAIL: gdb.base/fullname.exp: set breakpoint by full path before loading symbols - built relative
FAIL: gdb.base/fullname.exp: set breakpoint by full path after loading symbols - built relative
...

First failure in more detail:
...
(gdb) file /data/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.base/fullname/fullname^M
Reading symbols from /data/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.base/fullname/fullname...^M
(gdb) break /data/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.base/fullname/tmp-fullname.c:21^M
No source file named /data/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.base/fullname/tmp-fullname.c.^M
Make breakpoint pending on future shared library load? (y or [n]) n^M
(gdb) FAIL: gdb.base/fullname.exp: set breakpoint by full path before loading symbols - built relative
...
Comment 1 Tom Tromey 2019-06-17 16:18:28 UTC
It works fine here.
I wonder what the difference could be in our setups.
Comment 2 Tom de Vries 2019-06-17 20:46:51 UTC
(In reply to Tom Tromey from comment #1)
> It works fine here.
> I wonder what the difference could be in our setups.

I think I figured it out.

I've got this symlink:
...
$ ls -la /home/vries/gdb_versions
lrwxrwxrwx 1 vries users 18 26 jun  2018 /home/vries/gdb_versions -> /data/gdb_versions
...

When I run:
...
$ pwd
/home/vries/gdb_versions/devel
$ ( cd build/gdb/; make check RUNTESTFLAGS=gdb.base/fullname.exp )
...
I see the FAILs.

But when I do:
...
$ cd $(pwd -P)
$ pwd
/data/gdb_versions/devel
$ ( cd build/gdb/; make check RUNTESTFLAGS=gdb.base/fullname.exp )
...
the FAILs are gone.