OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

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:
Fred Fish 2002-04-05 00:30:09 +00:00
parent 2b9dd17b2f
commit cd72150368
2 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gdb/testsuite/ChangeLog
View File

@ -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.

6
gdb/testsuite/gdb.base/step-test.exp
View File

@ -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"]" \