#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 anevilyak): Replying to [comment:5 phoudoin]: > Or that the textual *.report form, export be moved to the Debugger UI part, and for the GUI made available under a `Save As` button. The report itself then could be displayed in UI tables, where user/developer could easily change sort order, copy/paste addresses, and differents states could be displayed with icons (running, locked, etc). It's already possible to save them via the UI, in the GUI: Tools -> Save Report, and the respective CLI save-report command. That having been said, I'd personally find that to be a bit overkill for the Debugger itself, though it'd certainly be an interesting possibility to export the data in a format that could be consumed by e.g. DebugAnalyzer for the kind of display/manipulation you're referring to. As far as the Threads go, the only problem there is that they have two potentially highly variable width columns, since in the case of either an actual crash or a debugger call you have the variable length messages from those in addition to the variable length thread name, which makes formatting a bit less fun without potentially wasting a lot of space. Can look into it though. -- Ticket URL: <http://dev.haiku-os.org/ticket/9697#comment:6> Haiku <http://dev.haiku-os.org> Haiku - the operating system.