[haiku-bugs] Re: [Haiku] #9697: Improve readability of crash reports
- From: "bonefish" <trac@xxxxxxxxxxxx>
- Date: Tue, 23 Apr 2013 12:00:11 -0000
#9697: Improve readability of crash reports
-------------------------------------+----------------------------
Reporter: bonefish | Owner: anevilyak
Type: enhancement | Status: in-progress
Priority: normal | Milestone: R1
Component: Applications/Debugger | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking:
Has a Patch: 0 | Platform: All
-------------------------------------+----------------------------
Comment (by bonefish):
Looks much better already. A few more suggestions:
* Images:
- Type column:
- Is not so important, so move it farther right, just before the name
column.
- Should be left-aligned.
- The long upper-case words look somewhat weird in a table. I would
use "app", "lib", "add-on", "system".
* Areas:
- The RAM Size can be omitted, I think.
- I guess an additional Size column would be nice after all. Base/End
have all the information, but it is hard to spot at a quick glance whether
an area is unusually large. The unit could be KiB to make the column a bit
more compact.
- Protection column:
- Should be left-aligned.
- I'd reserve space for the standard protection flags and display
them in the following manner:
{{{
r-x s
r--rw-
r-x Sk
}}}
- An index for the abbreviations would be nice. Just one ore two
lines below the table.
- Locking column: Should be left-aligned. I'd also use lower case.
* I agree with phoudoin that the Active Threads section look a bit untidy
now. Due to the additional information printed for crashed threads a table
might not be the best choice, though. Maybe something like this:
{{{
thread 3321: team 3320 debug task
thread 3351: worker
thread 3352: DebugReportGenerator
thread 3353: team 3349 debug listener
thread 3354: team debugger
state: Exception (Segment violation)
Frame IP Function Name
-----------------------------------------------
...
thread 3374: w>/Data/returnvaluetest (3349)
}}}
That is, omit the state for running threads and print other states in
the next line(s). Maybe also sort the list such that the boring threads
come first (or last).
@phoudoin: I don't think there's a lot to be gained from a GUI application
displaying the data. The crash reports are stack traces on steroids with a
lot of nice information that help with a first assessment of the problem
and, in some cases, even to understand it sufficiently. But I don't think
it's worth to develop them into something that allows sophisticated post
mortem debugging. The best tool for that purpose are core dumps. It
shouldn't be that much work to implement the required kernel support nor
should the support in Debugger be particularly complicated to do either
(mostly an alternate `DebuggerInterface` implementation).
--
Ticket URL: <http://dev.haiku-os.org/ticket/9697#comment:7>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
