hxcppdbg
hxcppdbg copied to clipboard
Aidan63
experimental hxcpp debugger using the windows debugger engine or lldb
Threads should be split into "Haxe" and "Native" threads. There are two ways we could go about detecting this. 1. Scan the stack of a thread and see if it...
A pause on entry option should be provided. The source maps will probably need to be updated to store the entry point so we can place a one shot breakpoint...
Currently cpp types such as `cpp.ConstPointer`, `cpp.Pointer`, etc don't have visualisers so will be treated as native objects. Should be easy enough to transform these into just pointers.
Having information such as stack frames, threads, etc, readable in the evaluator could be useful. Maybe some sort of singleton `hxcppdbg.Debugger` object, the debugger may want to start to have...
Most other languages treat curly brackets as someting what can be stepped onto, currently curly brackets are ignored. This could be tricky as haxe doesn't require curly brackets, so the...
Breakpoints should be able to have conditions applied to them, e.g. - Specific expression evaluates to true. - Breakpoint has been hit a specific number of times.
Currently the type of generic arguments are just `?`. The sourcemap should be updated so that the type of generic arguments are stored. We can't really read this back from...
Currently classes, arrays, and anon objects are the only supported types for keying into dynamic maps in the evaluator. Ints, Floats, and Maps should be supported as keys.
All integer and floats regardless of their size are stored in the same `ModelData` enum constructor. This means Int64s get truncated and there is no proper structured view of native...
Static variables are currently unsupported. Ideally these would be displayed in several ways. - For DAP, a new "statics" scope which contains all statics for type which is calling the...