PR# 12078 Internal Error halting debugger
Problem Report Summary
Submitter: peter_gummer
Category: EiffelStudio
Priority: High
Date: 2007/02/20
Class: Bug
Severity: Serious
Number: 12078
Release: 6.0.6.6451
Confidential: No
Status: Closed
Responsible:
Environment: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1
Synopsis: Internal Error halting debugger
Description
The Internal Error below occurred when I hit Shift+F5. In recent hours EiffelStudio has crashed several times, making an error noise, leaving multiple icons in the Windows task bar, not painting itself properly, etc. Usually I exited as soon as these tell-tale signs occurred, although once I had to force quit it. Now, while debugging, I have lost all of EiffelStudio's tools except the Call Stack and Features. The Feature Relation tool is completely gone, and the View | Tools menu doesn't bring it back. Because this is useless for debugging, I hit Shift+F5. Then the Internal Error appeared. After clicking the Ignore button, the status bar says "Application exited", but it still has the corrupted debugger layout rather than the normal layout, and the "Switching to normal mode" is sitting in the middle of the screen. At the Windows command line, when I type the "tasklist" command I see these: ec.exe 1296 Console 0 119,004 K ecdbgd.exe 1752 Console 0 2,092 K But my application does not appear in the task list, so the message in EiffelStudio's status bar appears to be correct.
To Reproduce
******************************** Thread exception *****************************
In thread Root thread 0x0 (thread id)
*******************************************************************************
-------------------------------------------------------------------------------
Class / Object Routine Nature of exception Effect
-------------------------------------------------------------------------------
Invalid_object parent @1 Segmentation violation:
<0000000000000000> (From EV_WIDGET) Operating system signal. Fail
-------------------------------------------------------------------------------
Invalid_object parent @1
<0000000000000000> (From EV_WIDGET) Routine failure. Fail
-------------------------------------------------------------------------------
SD_MULTI_DOCK_AREA editor_parent @4
<0000000005D571F0> Routine failure. Fail
-------------------------------------------------------------------------------
SD_CONFIG_MEDIATOR save_tools_config_with_name @3
<0000000004FF19B0> Routine failure. Fail
-------------------------------------------------------------------------------
SD_CONFIG_MEDIATOR save_tools_config @1
<0000000004FF19B0> Routine failure. Fail
-------------------------------------------------------------------------------
SD_DOCKING_MANAGER save_tools_config @2
<0000000005C4A628> Routine failure. Fail
-------------------------------------------------------------------------------
EB_DEBUGGER_MANAGER save_debug_docking_layout @1
<0000000005ED8A18> Routine failure. Fail
-------------------------------------------------------------------------------
EB_DEBUGGER_MANAGER unraise @10
<0000000005ED8A18> Routine failure. Fail
-------------------------------------------------------------------------------
EB_DEBUGGER_MANAGER on_application_quit @13
<0000000005ED8A18> Routine failure. Fail
-------------------------------------------------------------------------------
APPLICATION_EXECUTION_CLASSIC
on_application_quit @1
<0000000004D376F0> (From APPLICATION_EXECUTION)
Routine failure. Fail
-------------------------------------------------------------------------------
APPLICATION_EXECUTION_CLASSIC
process_termination @3
<0000000004D376F0> (From APPLICATION_EXECUTION)
Routine failure. Fail
-------------------------------------------------------------------------------
APPLICATION_EXECUTION_CLASSIC
kill @4
<0000000004D376F0> Routine failure. Fail
-------------------------------------------------------------------------------
EB_EXEC_QUIT_CMD kill @2
<0000000005EE3FC8> Routine failure. Fail
-------------------------------------------------------------------------------
EB_DISCARDABLE_CONFIRMATION_DIALOG
show_modal_to_window @3
<0000000004FD5C00> (From DISCARDABLE_CONFIRMATION_DIALOG)
Routine failure. Fail
-------------------------------------------------------------------------------
EB_EXEC_QUIT_CMD ask_and_kill @3
<0000000005EE3FC8> Routine failure. Fail
-------------------------------------------------------------------------------
EB_EXEC_QUIT_CMD execute @2
<0000000005EE3FC8> Routine failure. Fail
-------------------------------------------------------------------------------
EV_NOTIFY_ACTION_SEQUENCE
call @21
<0000000005EE4018> (From ACTION_SEQUENCE) Routine failure. Fail
-------------------------------------------------------------------------------
EV_NOTIFY_ACTION_SEQUENCE
call @3
<0000000005EE4018> (From EV_LITE_ACTION_SEQUENCE)
Routine failure. Fail
-------------------------------------------------------------------------------
EV_TITLED_WINDOW_IMP
on_accelerator_command @1
<0000000005D58A88> (From EV_WINDOW_IMP) Routine failure. Fail
-------------------------------------------------------------------------------
EV_TITLED_WINDOW_IMP
on_wm_command @18
<0000000005D58A88> (From WEL_COMPOSITE_WINDOW)
Routine failure. Fail
-------------------------------------------------------------------------------
EV_TITLED_WINDOW_IMP
process_message @8
<0000000005D58A88> (From WEL_COMPOSITE_WINDOW)
Routine failure. Fail
-------------------------------------------------------------------------------
WEL_DISPATCHER window_procedure @7
<0000000005BF37C0> (From WEL_ABSTRACT_DISPATCHER)
Routine failure. Retry
===============================================================================
Problem Report Interactions
The call stack is a bad result of previous docking operations. If all previous docking operations correct, the fault in the call stack will not happen. From your description, I don't know the exact error cause this call stack. However, at revision#67310, we handled the corrupted widget structure case when saving widget layouts. So at least this error call stack will not happen after revision#67310. Thanks for your report.