#11883: Debugger fails to parse debug output generated by rustc/llvm -------------------------------------+---------------------------- Reporter: nielx | Owner: anevilyak Type: enhancement | Status: new Priority: low | 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:3 nielx]: > Question: not recognizing the source file, where would I start? That depends on which of the above two problems it's hitting ; if it's failing to parse the actual DWARF output due to hitting a construct it doesn't know how to handle, then it will wind up falling back to basic disassembly. If that's the case, then tracking down what it's not able to handle will entail enabling some tracing via http://cgit.haiku- os.org/haiku/tree/build/config_headers/apps_debugger_config.h ; note that you can create a copy of this file in the subdir build/user_config_headers and modify it there for your personal uses. I would start by enabilng {{{ APPS_DEBUGGER_TRACE_DWARF_DIE }}} and possibly also {{{ APPS_DEBUGGER_TRACE_IMAGES }}}. If you then build Debugger with those flags enabled, and try running it against your rust binary from the CLI, you should get a fair amount of output from the DWARF parsing process, which should also indicate an error if it hits one. Unfortunately, there isn't currently much in the way of documentation for Debugger's internals, so we'll have to take this as we go with regards to finding problems. The lower level parsing code for handling DWARF is primarily in the various files comprising the dwarf/ subdir in any case. I'd suggest taking this to email from here on out so we don't wind up cluttering the ticket in any case though. -- Ticket URL: <https://dev.haiku-os.org/ticket/11883#comment:4> Haiku <https://dev.haiku-os.org> Haiku - the operating system.