diff options
| author | Fred Fish <fnf@specifix.com> | 2002-04-05 00:30:09 +0000 |
|---|---|---|
| committer | Fred Fish <fnf@specifix.com> | 2002-04-05 00:30:09 +0000 |
| commit | cd72150368372ac633adfe8e9c59c82274b3cd70 (patch) | |
| tree | b6b8f277ce7d008faa202d6b63d28905a60488e1 /gdb | |
| parent | 2b9dd17b2f1870918142552043f5fb9351827871 (diff) | |
| download | fsf-binutils-gdb-cd72150368372ac633adfe8e9c59c82274b3cd70.zip fsf-binutils-gdb-cd72150368372ac633adfe8e9c59c82274b3cd70.tar.gz fsf-binutils-gdb-cd72150368372ac633adfe8e9c59c82274b3cd70.tar.bz2 | |
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.
Diffstat (limited to 'gdb')
| -rw-r--r-- | gdb/testsuite/ChangeLog | 5 | ||||
| -rw-r--r-- | gdb/testsuite/gdb.base/step-test.exp | 6 |
2 files changed, 11 insertions, 0 deletions
diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog index 92bb9cf..1a36ded 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -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. diff --git a/gdb/testsuite/gdb.base/step-test.exp b/gdb/testsuite/gdb.base/step-test.exp index 6756b5d..9a21136 100644 --- a/gdb/testsuite/gdb.base/step-test.exp +++ b/gdb/testsuite/gdb.base/step-test.exp @@ -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"]" \ |