aboutsummaryrefslogtreecommitdiff
path: root/gdb/gdb_regex.c
diff options
context:
space:
mode:
authorTom Tromey <tom@tromey.com>2021-08-06 16:07:27 -0600
committerTom Tromey <tom@tromey.com>2021-08-23 14:14:20 -0600
commitd30c6bef12b2021211054f8a1672bc675a5cecb5 (patch)
treeeff39c72319ad8b3314998bc25a42a00d2f77945 /gdb/gdb_regex.c
parenta9680e0e54cfd8a12ddb1a583b4acb96dc2bbdbd (diff)
downloadgdb-d30c6bef12b2021211054f8a1672bc675a5cecb5.zip
gdb-d30c6bef12b2021211054f8a1672bc675a5cecb5.tar.gz
gdb-d30c6bef12b2021211054f8a1672bc675a5cecb5.tar.bz2
Fix a latent bug in dw2-ranges-overlap.exp
dw2-ranges-overlap.exp creates a program where a psymtab has two address ranges, and a function without debug info whose address is between these two ranges. Then it sets a breakpoint on this function and runs to it, expecting that the language should remain "auto; c" when stopped. However, this test case also has a "main" function described (briefly) in the DWARF, and this function is given language C++. Also, a breakpoint stop sets the current language to the language that was used when setting the breakpoint. My new DWARF scanner decides that this "main" is the main program and sets the current language to C++ at startup, causing this test to fail. This patch fixes the test in a simple way, by introducing a new function that takes the place of "main" in the DWARF. I think this still exercises the original problem, but also avoids problems with my branch. It seemed safe to me to submit this separately.
Diffstat (limited to 'gdb/gdb_regex.c')
0 files changed, 0 insertions, 0 deletions