This is the mail archive of the gdb-prs@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

gdb/14: FAIL: gdb.base/commands.exp: continue in infrun_breakpoint_command_test



>Number:         14
>Category:       gdb
>Synopsis:       FAIL: gdb.base/commands.exp: continue in infrun_breakpoint_command_test
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jan 29 06:28:01 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     Michael Chastain
>Release:        sourceware cvs gdb
>Organization:
>Environment:
Red Hat Linux 7 native
But the bug does not depend on environment.
>Description:
FAIL: gdb.base/commands.exp: continue in infrun_breakpoint_command_test

The test script sets a breakpoint and then creates a command list for the breakpoint.  The command list is:

  step
  step
  step
  step
  bt

The test script expects the four step commands and the bt command to execute.  But according to the GDB manual section on Breakpoint Command Lists (gdb/doc/gdb.texinfo):

  You can use breakpoint commands to start your program up again.  Simply use the "continue" command, or "step", or any other command that resumes execution.

  Any other commands in the command list, after a command that resumes execution, are ignored.  This is because any time you resume execution (even with a simple "next" or "step"), you may encounter another breakpoint---which could have its own command list, leading to ambiguities about which list to execute.

gdb is behaving in conformance to the manual.  The test script is wrong.
>How-To-Repeat:
Run the gdb testsuite.
Look at the gdb.log lines for this failure.
>Fix:
Change the acceptance criteria for this test to succeed just when exactly one "step" command executes.
Check that the test script right after this test does not depend on how many "step" commands were executed (this is probably already true).
>Release-Note:
>Audit-Trail:
>Unformatted:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]