diff options
| author | Luis Machado <lgustavo@codesourcery.com> | 2016-04-13 15:22:14 -0500 |
|---|---|---|
| committer | Luis Machado <lgustavo@codesourcery.com> | 2016-04-13 15:22:14 -0500 |
| commit | 7d49b1d0b08426c650a69a6c4971cba56a4e6af1 (patch) | |
| tree | 4fbab43003df76da6cd767c867f253bf95a9d59c /bfd/version.h | |
| parent | 57d1de9cf3ba8dd98eaf4a3d131c05ec4c49779d (diff) | |
| download | gdb-7d49b1d0b08426c650a69a6c4971cba56a4e6af1.zip gdb-7d49b1d0b08426c650a69a6c4971cba56a4e6af1.tar.gz gdb-7d49b1d0b08426c650a69a6c4971cba56a4e6af1.tar.bz2 | |
Test GDB connection to GDBserver with no symbol files
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.
Diffstat (limited to 'bfd/version.h')
0 files changed, 0 insertions, 0 deletions