3 ms·
Perhaps the bug we chose to demo there is not representative of most bugs, but the underlying bug is in C code and Brendan Gregg, the person who debugged it "fo
by roca 5y ago
Perhaps the bug we chose to demo there is not representative of most bugs, but the underlying bug is in C code and Brendan Gregg, the person who debugged it "for real", debugged it using gdb. The erroneous state in this case is in ncurses, packaged as a system library, so using print debugging here would require building ncurses from source and wedging that into LLVM/Python somehow. So no, I don't believe your claim.
- cptskippy 5y agoI recognize that there are bugs that exist in downstream packages and some developers take it upon themselves to debug and troubleshoot those occurrences, which we should appreciate. I think we should all recognize that as a special case and not the norm. Most developers, myself included, lack the knowledge or skill to do that. I would speculate that most developers, once they identify a bug in a downstream package, would instead either go online to find consensus around the bug and report it to the maintainer of that package, or just find an alternative solution.
- deleted 5y ago[deleted]