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]
Other format: [Raw text]

gdb/475: Command to force abort when internal error ...



>Number:         475
>Category:       gdb
>Synopsis:       Command to force abort when internal error ...
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Sat Apr 06 14:08:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     ac131313@redhat.com
>Release:        2002-04-05
>Organization:
>Environment:

>Description:
When running a testsuite, GDB occasionally detects an internal error.  The internal error is ok, the problem is that GDB prompts the user for what to do next and that stalls the testsuite.

Suggest a command to explicitly disable the internal-error prompt (quit? dump core?) and automatically dump core.  That way making the testsuite fall over quicker.
>How-To-Repeat:

>Fix:

>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]