Valentin Churavy
Valentin Churavy
How does that work with exception stacks? In the above I have two stacked exceptions.
Yeah and the location is not enough information for Cthulhu, so we would need to store the stackframe itself.
`Method`s are not sufficient I need `MethodInstance`s.
Gdb has a commands feature. A set of commands that can be executed when a breakpoint is triggered. Fantastic to collect information about the 100 times a breakpoint got triggered...
Take a look at https://github.com/ronisbr/TerminalPager.jl and our codeview functions are here: https://github.com/JuliaDebug/Cthulhu.jl/blob/master/src/codeview.jl and printed in places like https://github.com/JuliaDebug/Cthulhu.jl/blob/6880b9e47f57625e890594e0d0e11c59393b4bb9/src/Cthulhu.jl#L301
Probably best to do that in two PRs and important to have a toggle to turn it off.
yeah that's not ideal. maybe we need a deeper integration between TerminalPager and TerminalMenu is needed
I think that is a fine idea, as long as we don't clutter up the UI, so we would need to attach meaning to other keys. I wanted to add...
Do you want the linenumber in the options that Cthulhu presents you, or just in the general debuginfo printing?
Do you need something more than: ``` Base.IRShow.debuginfo[:default] = Base.IRShow.debuginfo[:source] @code_typed debuginfo=:source f() ```? On Mon, Feb 4, 2019 at 10:35 PM Chris Foster wrote: > I think it would...