diff options
| author | Tom de Vries <tdevries@suse.de> | 2025-10-08 22:32:00 +0200 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2025-10-08 22:32:00 +0200 |
| commit | 40305c9581b2b73e7f6f9a124a5e470449c623ef (patch) | |
| tree | ecb47e7f37ae44bad502efd210dc62821e671bb5 /gdb/testsuite/gdb.python/py-cmd-exception.py | |
| parent | 733ccb8b3fd5422606d5c1ebeba246fa89c8f9ae (diff) | |
| download | binutils-40305c9581b2b73e7f6f9a124a5e470449c623ef.zip binutils-40305c9581b2b73e7f6f9a124a5e470449c623ef.tar.gz binutils-40305c9581b2b73e7f6f9a124a5e470449c623ef.tar.bz2 | |
[gdb/testsuite] Fix bp loc in gdb.server/fetch-exec-and-args.exp
With test-case gdb.server/fetch-exec-and-args.exp, on aarch64-linux I run into:
...
(gdb) break 28^M
Breakpoint 1 at 0xfffff7fd7b8c: file ../sysdeps/aarch64/dl-start.S, line 30.^M
(gdb) continue^M
Continuing.^M
^M
Breakpoint 1, _start () at ../sysdeps/aarch64/dl-start.S:30^M
30 mov x0, sp^M
(gdb) PASS: $exp: packet=on: test_exec_and_arg_fetch: \
continue to breakpoint: run to breakpoint
print argc^M
No symbol "argc" in current context.^M
(gdb) FAIL: $exp: packet=on: test_exec_and_arg_fetch: print argc
...
The problem is that the "break 28" is not specific about the file.
Fix this by setting the breakpoint on fetch-exec-and-args.c:28.
Tested on aarch64-linux.
PR testsuite/33522
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=33522
Diffstat (limited to 'gdb/testsuite/gdb.python/py-cmd-exception.py')
0 files changed, 0 insertions, 0 deletions
