mirror of
https://github.com/darlinghq/darling-gdb.git
synced 2024-11-25 05:00:01 +00:00
2002-04-04 Fred Fish <fnf@redhat.com>
* gdb.base/step-test.exp: Update comment regarding stopping in memcpy/bcopy calls inserted as part of the compiler runtime.
This commit is contained in:
parent
2b9dd17b2f
commit
cd72150368
@ -1,3 +1,8 @@
|
||||
2002-04-04 Fred Fish <fnf@redhat.com>
|
||||
|
||||
* gdb.base/step-test.exp: Update comment regarding stopping in
|
||||
memcpy/bcopy calls inserted as part of the compiler runtime.
|
||||
|
||||
2002-04-04 Michael Snyder <msnyder@redhat.com>
|
||||
|
||||
* gdb.base/ovlymgr.c: Add overlay event breakpoint support.
|
||||
|
@ -204,6 +204,12 @@ test_i "nexti over function" "nexti" \
|
||||
# argument. Opinion is bitterly divided about whether this is the
|
||||
# right behavior for GDB or not, but we'll catch it here, so folks
|
||||
# won't forget about it.
|
||||
# Update 4/4/2002 - Regardless of which opinion you have, you would
|
||||
# probably have to agree that gdb is currently behaving as designed,
|
||||
# in the absence of additional code to not stop in functions used
|
||||
# internally by the compiler. Since the testsuite should be checking
|
||||
# for conformance to the design, the correct behavior is to accept the
|
||||
# cases where gdb stops in memcpy/bcopy.
|
||||
|
||||
gdb_test \
|
||||
"break [gdb_get_line_number "step-test.exp: large struct by value"]" \
|
||||
|
Loading…
Reference in New Issue
Block a user