Yes - but it hasn't gotten much attention over the last two years (and sorry, I thought I had mentioned Debug.jl in my initial post).
https://github.com/toivoh/Debug.jl/graphs/code-frequency Feels like there could be a lot of work there that would be tremendously helpful, but not sure if people are focused on it (and instead attention is on being able to seamlessly navigate from julia -> c). Is anyone working on extending the functionality there, or is it viewed as a developmental dead end? Michael On Tuesday, June 2, 2015 at 11:31:04 AM UTC-4, Tim Holy wrote: > > https://github.com/toivoh/Debug.jl > <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Ftoivoh%2FDebug.jl&sa=D&sntz=1&usg=AFQjCNFVItS_nt9vtR2lzYEoYZu8ZhxJwA> > > > --Tim > > On Tuesday, June 02, 2015 08:21:51 AM Michael Turok wrote: > > Right, but I'm interested in an debugger that would work without a > custom > > compilation of LLVM, and would work with a stock release of julia 0.3*. > > > > On Tuesday, June 2, 2015 at 11:11:09 AM UTC-4, Isaiah wrote: > > > https://groups.google.com/d/msg/julia-dev/gcZ5dZJni5o/VYaLkCd756cJ > > > > > > On Tue, Jun 2, 2015 at 11:07 AM, Michael Turok <michae...@gmail.com > > > > > > <javascript:>> wrote: > > >> Is there anyone currently focusing on building an AST-level debugger > that > > >> can navigate stack frames and not require modifying code to insert > > >> instrumentation stubs, etc? > > >> > > >> While the LLVM JIT debugger referenced in the below thread from > December > > >> 2013 is interesting, seems like there might be more low-lying fruit > out > > >> there..... > > >> > > >> > > >> > https://groups.google.com/forum/#!searchin/julia-users/debugger/julia-use > > >> rs/zEqWxn7HDVo/ZTRZh4ziR9kJ > >
