No CrashDaemon running for system services: difficult to debug early user mode crashes
I have been working on some changes, which somehow are causing WindowServer to crash early on. It is incredibly difficult to get any stack traces to help pinpoint what the problem is. This is all I get:
1.444 WindowServer(11:11): update_virtual_and_physical_rects for screen #0: [0,0 1024x768]
1.458 WindowServer(11:11): update_virtual_and_physical_rects for screen #0: [0,0 1024x768]
1.468 WindowServer(11:11): update_virtual_and_physical_rects for screen #0: [0,0 1024x768]
1.468 WindowServer(11:11): update_virtual_and_physical_rects for screen #1: [1024,0 1024x768]
1.557 WindowServer(11:11): update_virtual_and_physical_rects for screen #1: [1024,0 1024x768]
1.557 WindowServer(11:11): update_virtual_and_physical_rects for screen #1: [1024,0 1024x768]
1.603 WindowServer(11:11): ASSERTION FAILED: m_has_value
././AK/Optional.h:215
1.603 [#0 WindowServer(11:11)]: Kernel + 0x00000000010d109e Kernel::Process::sys$dump_backtrace() +0xce
1.603 [#0 WindowServer(11:11)]: Kernel + 0x000000000109c11b Kernel::Syscall::handle(Kernel::RegisterState&, unsigned long, unsigned long, unsigned long, unsigned long, unsigned long) [clone .localalias] +0x8cb
1.603 [#0 WindowServer(11:11)]: Kernel + 0x000000000109de32 syscall_handler +0x902
1.603 [#0 WindowServer(11:11)]: Kernel + 0x0000000001666eb1 syscall_entry +0x51
1.603 [#0 WindowServer(11:11)]: Terminating WindowServer(11) due to signal 6
1.603 [#0 Finalizer Task(5:5)]: Backtrace:
0x00000000deadc0de Kernel::Processor::switch_context(Kernel::Thread*&, Kernel::Thread*&) + 0x383
1.603 [#0 Finalizer Task(5:5)]: Process 'WindowServer' exited with the veil left open
1.603 [#0 Finalizer Task(5:5)]: Generating coredump for pid: 11
1.648 SystemServer(8:8): Service WindowServer has exited with exit code 6
1.651 SystemServer(8:8): Trying again
1.695 WindowServer(25:25): update_virtual_and_physical_rects for screen #0: [0,0 1024x768]
1.707 WindowServer(25:25): update_virtual_and_physical_rects for screen #0: [0,0 1024x768]
1.707 WindowServer(25:25): update_virtual_and_physical_rects for screen #0: [0,0 1024x768]
1.707 WindowServer(25:25): update_virtual_and_physical_rects for screen #1: [1024,0 1024x768]
1.786 WindowServer(25:25): update_virtual_and_physical_rects for screen #1: [1024,0 1024x768]
1.786 WindowServer(25:25): update_virtual_and_physical_rects for screen #1: [1024,0 1024x768]
1.802 WindowServer(25:25): ASSERTION FAILED: m_has_value
././AK/Optional.h:215
1.806 [#0 WindowServer(25:25)]: Kernel + 0x00000000010d109e Kernel::Process::sys$dump_backtrace() +0xce
1.806 [#0 WindowServer(25:25)]: Kernel + 0x000000000109c11b Kernel::Syscall::handle(Kernel::RegisterState&, unsigned long, unsigned long, unsigned long, unsigned long, unsigned long) [clone .localalias] +0x8cb
1.806 [#0 WindowServer(25:25)]: Kernel + 0x000000000109de32 syscall_handler +0x902
1.806 [#0 WindowServer(25:25)]: Kernel + 0x0000000001666eb1 syscall_entry +0x51
1.806 [#0 WindowServer(25:25)]: Terminating WindowServer(25) due to signal 6
1.806 [#0 Finalizer Task(5:5)]: Backtrace:
0x00000000deadc0de Kernel::Processor::switch_context(Kernel::Thread*&, Kernel::Thread*&) + 0x383
1.806 [#0 Finalizer Task(5:5)]: Process 'WindowServer' exited with the veil left open
1.806 [#0 Finalizer Task(5:5)]: Generating coredump for pid: 25
1.862 SystemServer(8:8): Service WindowServer has exited with exit code 6
1.862 SystemServer(8:8): Third time's the charm?
1.897 WindowServer(26:26): update_virtual_and_physical_rects for screen #0: [0,0 1024x768]
1.908 WindowServer(26:26): update_virtual_and_physical_rects for screen #0: [0,0 1024x768]
1.908 WindowServer(26:26): update_virtual_and_physical_rects for screen #0: [0,0 1024x768]
1.908 WindowServer(26:26): update_virtual_and_physical_rects for screen #1: [1024,0 1024x768]
1.978 WindowServer(26:26): update_virtual_and_physical_rects for screen #1: [1024,0 1024x768]
1.978 WindowServer(26:26): update_virtual_and_physical_rects for screen #1: [1024,0 1024x768]
1.981 WindowServer(26:26): ASSERTION FAILED: m_has_value
././AK/Optional.h:215
1.981 [#0 WindowServer(26:26)]: Kernel + 0x00000000010d109e Kernel::Process::sys$dump_backtrace() +0xce
1.981 [#0 WindowServer(26:26)]: Kernel + 0x000000000109c11b Kernel::Syscall::handle(Kernel::RegisterState&, unsigned long, unsigned long, unsigned long, unsigned long, unsigned long) [clone .localalias] +0x8cb
1.981 [#0 WindowServer(26:26)]: Kernel + 0x000000000109de32 syscall_handler +0x902
1.981 [#0 WindowServer(26:26)]: Kernel + 0x0000000001666eb1 syscall_entry +0x51
1.981 [#0 WindowServer(26:26)]: Terminating WindowServer(26) due to signal 6
1.981 [#0 Finalizer Task(5:5)]: Backtrace:
0x00000000deadc0de Kernel::Processor::switch_context(Kernel::Thread*&, Kernel::Thread*&) + 0x383
1.981 [#0 Finalizer Task(5:5)]: Process 'WindowServer' exited with the veil left open
1.985 [#0 Finalizer Task(5:5)]: Generating coredump for pid: 26
2.032 SystemServer(8:8): Service WindowServer has exited with exit code 6
2.032 SystemServer(8:8): Giving up on WindowServer. Good luck!
It appears that CrashDaemon only runs for anon once logged in. It would be nice to have it (or another instance) run regardless, and in absence of a GUI at least log a crashdump to the debug log (see #11428).
SerenityOS / serenity
The Serenity Operating System 🐞
30.6k
Contributors get 100% of received funds after fees
How does funding with Polar work?
1
Pay now to fund the work behind this issue.
2
Get updates on progress being made.
3
Maintainer is rewarded once the issue is completed.
FAQ
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too