[haiku-commits] Re: haiku: hrev53104 - src/apps/debugger/user_interface/gui/team_window src/system/kernel/locks headers/private/kernel src/servers/debug
- From: looncraz <looncraz@xxxxxxxxxxxx>
- To: haiku-commits@xxxxxxxxxxxxx
- Date: Fri, 3 May 2019 10:20:34 -0500
On 03/05/2019 09.57, Adrien Destugues wrote:
I don't think the feature should be hidden in a more complex way than
it already is.
I have to disagree.. but I'd like to see a very different setup.
Create an "Advanced" or "More" button that allows me to choose to never
enter the slow mess that the Debugger can sometimes be. I just want a
quick back-trace 99% of the time when a crash happens. Tell me where it
crashed and I will find why it crashed usually without any other efforts.
The options should include, but not be limited to:
"See stack trace."
"Write stack trace to file."
"Dump memory to file."
"Attempt to continue (not recommended)."
"Report to author."
"Open Debugger"
"Quit application"
(I see this as a simple radio button list).
The main crash dialog would then have options "Quit" "Advanced" "Report"
The "Report" button will correspond to the "Report to author" option in
the advanced menu, it will create a report archive, asking the user
where to save it. The report would probably not need much more than a
stack trace and some general system information (CPU, memory, memory
used, swap space).
A standardized method to report issues to a package author would work
extremely well with this - if we know the author, then the package
management system can send these crashes to the depot to link with each
application - and applications can have a crash count metric as well as
some auto parsing to determine if there's a common crash source.
Any application in the system would then receive some free telemetry
that is open and well documented.
Those are my thoughts, anyway.
--The loon
Other related posts:
