When registrar crashes, debugger cannot be started and attached to it

[pulkomandy]

So I'm trying to run the webkit testsuite...

After several hours it crashed again. The screen became white and consoled grabbed the keyboard input as if debugger was about to be attached. But it didn't happen. System appears to still be running (I had a terminal showing the syslog, which continued to scroll by, for example, activitymonitor is still live, etc) but I can't open menus in my Terminal windows for example. I could switch workspaces. I could still select icons on the desktop but trying to open one finally froze the system.

Before that I took a picture of the syslog message:

vm_soft_fault: va 0x1100000 not covered by area in address space
vm_page_fault: vm_soft_fault returned "Bad address" on fault at 0x1100608, ip 0xff72aa, write 0, user 1, thread 0x3c0
debug_server: thread 960 entered the debugger: Segment violation
stack trace, current PC 0xff72aa PopCommand__13MessagingArea + 0x3e
(0x70184028) 0xff7f8b _CommandProcessor__16MessagingService + 0xc7
(0x70184068) 0xff7ebb _CommandProcessorEntry__16MessagingServicePv + 0x1f
(0x70184098) 0xdc7cdd thread_entry

[pulkomandy]

I can still enter KDL. Apparently this is the "messaging command processor" thread from registrar, so I guess with the registrar crashed, Debugger can't start and that's how I end up in that half-broken situation?

[X512]

Its probably better to run testsuite in test_app_server.

[anevilyak]

At the moment I'm uncertain as to why this would fail. When attaching to registrar or app_server, the debugger is loaded in cli mode, which avoids creating a BApplication object for precisely this reason. It's possible something else is being instantiated that results in a registrar interaction behind the scenes, but I'm not sure what it would be right now without further stuffing and/or being able to reproduce it.

When you entered KDL, was the debugger team visible at all? If so, what states were its threads in?

[pulkomandy]

I didn't think of checking that. And now I have rebooted the machine. I'll see if it reproduces or if I finally manage to run the webkit testsuite completely today.