tromey
Re:Writing a Linux Debugger (2017)
on Wednesday June 14, 2023 @05:09PM (#36332694)
gdb uses BFD for object file access but has its own DWARF reader.
Re:The State of Linux Debuggers
on Tuesday December 15, 2020 @10:20AM (#25431061)
This was https://sourceware.org/bugzilla/show_bug.cgi?id=25348, fixed in June. I believe the fix is in the latest release.
Re:The State of Linux Debuggers
on Sunday December 13, 2020 @03:03PM (#25409677)
Yes, just nobody has implemented it. It's kind of a pain. Also it brings up the question of whether GDB ought to implement a terminal so you can debug curses applications inside the TUI, which is even more of a pain.
Re:The State of Linux Debuggers
on Sunday December 13, 2020 @03:00PM (#25409640)
No-one maintains the Pascal support in GDB. In fact, I think the test suite doesn't even run any more (at least for me, FPC seems totally broken). This is an area where a volunteer could make useful progress pretty easily.
Re:Maybe you don't need Rust and WASM to speed up your JS
on Monday February 19, 2018 @12:35PM (#16414249)
> Source maps are a debug tool. Why does the performance matter?
If the source map decoder is slow, then the debugger feels slow.
Re:Rust in 2017: what we achieved
on Thursday December 21, 2017 @06:25PM (#15983883)
Rust support landed in gdb 7.12 (released October 2016). It has some rough edges; and some missing spots (mostly caused by insufficient debuginfo).
I'm working full time on Rust debugging now. My basic plan is to write a Rust plugin for lldb (WIP branch https://github.com/tromey/lldb/tree/rust); then update LLVM, rustc, lldb, and gdb in sync to add support for missing features.
I'm interested in bug reports and other constructive feedback.