Opened 5 years ago
Last modified 5 years ago
#16011 new enhancement
Default to "save-report" for critical system components
| Reported by: | pulkomandy | Owned by: | anevilyak |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | Servers/debug_server | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
When app_server or input_server crashes, a CLI debugger automatically opens. Instead the default behavior, at least in beta releases, should be to save a debug report automatically to the desktop.
Users keep confusing this with the kernel debugging land, which creates unprecise bugreports, and more annoyingly, it is not possible to recover completely from these (even if launch daemon manages to restart the app) because consoled keeps grabbing the keyboard input.
Having the report go on the desktop and attempting to restart app_server or input_server would be more user friendly.
Note:
See TracTickets
for help on using tickets.
To some extent this can be solved already by supplying a custom debug_server settings file in b2, since it supports configuring default actions by team:
https://git.haiku-os.org/haiku/tree/src/servers/debug/DebugServer.cpp#n104
However, this would not (currently) include automatically restarting the corresponding subsystem. In the case of input_server, I *believe* launch_daemon would take care of it implicitly, but for registrar or app_server that approach may be problematic, since that has effectively invalidated critical communications links as well as application state. As such, for the latter two I would advocate for a disk sync + reboot after saving the report. Thoughts?