[haiku-bugs] Re: [Haiku] #9697: Improve readability of crash reports

  • From: "anevilyak" <trac@xxxxxxxxxxxx>
  • Date: Wed, 24 Apr 2013 12:18:57 -0000

#9697: Improve readability of crash reports
-------------------------------------+----------------------------
   Reporter:  bonefish               |      Owner:  anevilyak
       Type:  enhancement            |     Status:  closed
   Priority:  normal                 |  Milestone:  R1
  Component:  Applications/Debugger  |    Version:  R1/Development
 Resolution:  fixed                  |   Keywords:
 Blocked By:                         |   Blocking:
Has a Patch:  0                      |   Platform:  All
-------------------------------------+----------------------------

Comment (by anevilyak):

 Replying to [comment:10 phoudoin]:
 > Now that's great, the detailed stack crawl of the debugged thread(s) is
 really nice.

 Note that's only available if we have the requisite debug info to dump
 variables though.

 > In the top header, could it be possible to show which gcc2/4 flavor is
 it?

 Currently we're only aware of that in the DWARF subsystem since we have to
 detect that to account for various differences in the format of .eh_frame.
 Will need to think about how to propagate that information back up to a
 level where the report generator could consume it, unless there's an
 alternative heuristic which can be used to detect that differently.

 Replying to [comment:11 bonefish]:
 > * The Image:Type column seems to be wider than necessary.

 Indeed, that one simply has an extraneous tab. Will deal with that.

 > * Areas:Locking is rather wide for the values actually in the column. I
 suppose it's just wide enough for the longest possible value. Maybe
 iterate once through the area list before printing it to determine the
 column width actually needed. That would also be useful for the ID
 columns.

 Indeed, its current width is based on the widest possible locking flag,
 namely "32-bit contiguous". Will see what I can do with that, though I
 suppose that one could also simply be shortened to "32-bit contig." or
 something in that vein.

 > * Semaphores: There's also a bit more spacing than usual between the
 Count and the Last Holder and between the Last Holder and the Name column.
 Though, maybe that was intentional.

 The space between Last Holder and Name is indeed due to another extra tab
 that can be eliminated. In the case of Count vs Last Holder though,
 there's only a single tab separator. The perceived additional space is
 simply due to being right aligned, the padding width there is actually
 based on the width of the column header though, so without shortening the
 latter in some way there'd be extra space regardless.

--
Ticket URL: <http://dev.haiku-os.org/ticket/9697#comment:12>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.

Other related posts: