mirror of
https://sourceware.org/git/binutils-gdb.git
synced 2024-11-30 21:44:19 +08:00
7d49b1d0b0
This test exercises the scenarios where we attempt to connect GDB to GDBserver in standard remote mode, query the symbol file path, attempt to open said symbol file on GDB's end and fail, causing the connection to drop abruptly. Regression-tested on x86-64/Ubuntu. With an unpatched GDB we should see this: FAIL: gdb.server/connect-with-no-symbol-file.exp: sysroot=: action=permission: connection to GDBserver succeeded (the program is no longer running) FAIL: gdb.server/connect-with-no-symbol-file.exp: sysroot=: action=delete: connection to GDBserver succeeded (the program is no longer running) FAIL: gdb.server/connect-with-no-symbol-file.exp: sysroot=target:: action=permission: connection to GDBserver succeeded (the program is no longer running) FAIL: gdb.server/connect-with-no-symbol-file.exp: sysroot=target:: action=delete: connection to GDBserver succeeded (the program is no longer running) A patched GDB should have full passes. gdb/testsuite/ChangeLog: 2016-04-13 Luis Machado <lgustavo@codesourcery.com> * gdb.server/connect-with-no-symbol-file.c: New file. * gdb.server/connect-with-no-symbol-file.exp: New file. |
||
---|---|---|
.. | ||
connect-stopped-target.c | ||
connect-stopped-target.exp | ||
connect-with-no-symbol-file.c | ||
connect-with-no-symbol-file.exp | ||
connect-without-multi-process.c | ||
connect-without-multi-process.exp | ||
ext-attach.c | ||
ext-attach.exp | ||
ext-restart.exp | ||
ext-run.exp | ||
ext-wrapper.exp | ||
file-transfer.exp | ||
no-thread-db.c | ||
no-thread-db.exp | ||
non-existing-program.exp | ||
server-exec-info.exp | ||
server-kill.c | ||
server-kill.exp | ||
server-mon.exp | ||
server-run.exp | ||
server.c | ||
solib-list-lib.c | ||
solib-list-main.c | ||
solib-list.exp | ||
transfer.txt | ||
wrapper.c | ||
wrapper.exp |