diff options
| author | Pedro Alves <pedro@palves.net> | 2022-03-30 14:31:56 +0100 |
|---|---|---|
| committer | Pedro Alves <pedro@palves.net> | 2022-05-17 10:31:36 +0100 |
| commit | 35b72e4e5baabef35b34db7f12c627e7232ee204 (patch) | |
| tree | 52c6107c68d7579c73a891eb528c1925cb0232ae /gdb/testsuite/gdb.python/py-parameter.exp | |
| parent | bc6004dfd2654e53d6f167b985b38ca780e79228 (diff) | |
| download | binutils-35b72e4e5baabef35b34db7f12c627e7232ee204.zip binutils-35b72e4e5baabef35b34db7f12c627e7232ee204.tar.gz binutils-35b72e4e5baabef35b34db7f12c627e7232ee204.tar.bz2 | |
gdb.base/scope.exp: Remove bogus gdb_test questions
This test is abusing the QUESTION/RESPONSE feature to send an
alternative command to GDB if the first command fails. Like so:
gdb_test "print 'scope0.c'::filelocal" \
"\\\$$decimal = 1" "print 'scope0.c'::filelocal at main" \
"No symbol \"scope0.c\" in current context.*" \
"print '$srcdir/$subdir/scope0.c'::filelocal"
So if 'scope0.c' doesn't work, we try again with
'$srcdir/$subdir/scope0.c'. I strongly suspect this is really an
obsolete test. I think that if '$srcdir/$subdir/scope0.c' works, then
'scope0.c' should have worked too, thus I'd think that if we pass due
to the question path, then it's a bug. So just remove the question
part passed to gdb_test.
Change-Id: I2acc99285f1d519284051b49693b5441fbdfe3cd
Diffstat (limited to 'gdb/testsuite/gdb.python/py-parameter.exp')
0 files changed, 0 insertions, 0 deletions