core-explorer

6 ms·

1.
by core-explorer 9mo ago
This is very cool. I am a big believer in tools analyzing a sequence of heap snapshots to automate the time-consuming parts of manual debugging. I am working on doing something similar in C++, where there is an additional obstacle of recrea
2.
by core-explorer 9mo ago
The extensions were voted into the upcoming DWARF 6 standard, e.g. https://dwarfstd.org/issues/211206.1.html
3.
by core-explorer 1y ago
debugging information is more precise than line numbers, it usually conveys line and column in a source file. Some debuggers make use of it when displaying the current program state, the major debuggers do not allow you to step into a speci
4.
Strong Typing and Debug Information and Decompilation = Heap Analysis for C++(core-explorer.github.io)
3 points by core-explorer 1y ago|1 comments
5.
by core-explorer 1y ago
I got tired of debugging the same kind of bugs over and over again. I can't make a dent in the overall quality of the legacy code base, so I decided to start writing a tool to automate the boring parts of debugging memory corruption an
6.
by core-explorer 1y ago
When you try to solve one problem involving two objects in three-dimensional space, you have a six-dimensional problem space. If you have two moving objects, you have a twelve-dimensional problem space. Higher dimensional spaces show up eve
7.
by core-explorer 1y ago
We usually don't talk about "the dimensions", we talk about the general case: n-dimensional spaces (theorems covering all dimensions simultaneously) or infinite-dimensional spaces (individual spaces covering all finite-dimens
8.
by core-explorer 2y ago
I know how to see the source in my debugger and I know how to see the disassembly. Which IDE will show me the compiler's internal IR if I want something in between?
9.
Debugging C++ is a UI nightmare(core-explorer.github.io)
39 points by core-explorer 2y ago|20 comments
10.
Core dump analyzer that runs in the browser(github.com)
3 points by core-explorer 2y ago|1 comments
11.
by core-explorer 2y ago
I felt under-challenged last year and realized that it is because I spend too much time debugging and not enough time writing software. So I did the obvious thing and spent the holiday season writing a new debugging tool instead of playing