diff options
| author | Kevin Buettner <kevinb@redhat.com> | 2019-10-12 23:12:29 -0700 |
|---|---|---|
| committer | Kevin Buettner <kevinb@redhat.com> | 2019-11-27 13:05:09 -0700 |
| commit | d22670f0780f4d296325d35049f0d57791ef6d73 (patch) | |
| tree | b68106270ac53e6115fe2a4645a060cf7b3df8e3 /gdb/jit.c | |
| parent | 8d9a2568651d55eb518d3ac6c0dd0b4719da7f77 (diff) | |
| download | gdb-d22670f0780f4d296325d35049f0d57791ef6d73.zip gdb-d22670f0780f4d296325d35049f0d57791ef6d73.tar.gz gdb-d22670f0780f4d296325d35049f0d57791ef6d73.tar.bz2 | |
Test case for BZ 25065
Running a GDB with the fix for BZ 25065 should cause these new tests
to all pass.
When run against a GDB without the fix, there will be 2 unresolved
testcases. This is what I see in the gdb.sum file when I try it using
a GDB without the fix:
ERROR: GDB process no longer exists
UNRESOLVED: gdb.dwarf2/imported-unit.exp: ptype main::Foo
ERROR: Couldn't send ptype main::foo to GDB.
UNRESOLVED: gdb.dwarf2/imported-unit.exp: ptype main::foo
These are "unresolved" versus outright failures due to the fact that
GDB dies (segfaults) during the running of the test.
gdb/testsuite/ChangeLog:
* gdb.dwarf2/imported-unit.exp: New file.
* gdb.dwarf2/imported-unit.c: New file.
Change-Id: I073fe69b81bd258951615f752df8e95b6e33a271
Diffstat (limited to 'gdb/jit.c')
0 files changed, 0 insertions, 0 deletions