Create your own GitHub profile
Sign up for your own profile on GitHub, the best place to host code, manage projects, and build software alongside 31 million developers.
Sign up
Pinned
2,271 contributions in the last year
Activity overview
Contribution activity
March 2019
Created a pull request in JuliaDebug/JuliaInterpreter.jl that received 26 comments
WIP: also build compiled calls for ccall
Here are the issues I have found so far: Problems with type parameters: Trying to use a function that has a type parameter in its return value (the…
+137
−30
•
26
comments
- WIP: show a nice stacktrace when breaking on error
- use Base.error_color to be consistent with Base for errors
- prevent erroring out of debugger if we add an argument to one of the JuliaInterpreter commands
- fix printing for evaluation level and make fr show the current level by default instead of level 1
- reexport some more breakpoint functionality
- fix fr showing the correct frame
- improve error message when julia repl is not loaded
- fix evals when the value is a symbols
- protect against files being out of sync with lineinfo in the method
- fix line info printing in bt
- prepare for 0.2.0 release
- implement a "floor" for the printing
- add a toggle for showing lowered code and refactor printing a bit
- step out wrapper calls
- fix showing keyword calls
- improve breakpoint printing
- use the exported break_on from JuliaInterpreter
- fix mixup between f and fr
- add toggle for Compiled mode
- fix f and fr
- refine breakpoint printing
- show breakpoints in source code, also remove some bold
- show a token for current line
- align line numbers to the right
- don't run recursive interpretation unless there is a chance of breaking
- Some pull requests not shown.
- fix bug when passing static parameters
- prevent expensive compilation of map / splatting
- fix assertion when breakpoint triggers during wrapper step through
- fix test from builtin check on 1.0
- Support :foreigncall to an SSAValue-referenced symbol (fixes #220)
- fix lookup for SSAValues in foreigncalls and quote the library if it is a symbol
- only unlink frames if exception will not be thrown to top level
- move maybe_assign! and get_return to commands.jl
- get rid of O(n^2) behavior in stack depth when enabling break_on(:error)
- make `show_backtrace` and `display_error` work for Frame
- add subtypes to compiled methods
- fix undef sparam in locals
- ensure si doesn't step over anything
- add a missing Meta to extract_args
- step out of wrapper calls
- RFC: step through kwprep in next_line
- add kwprep to docs to fix doc build
- allow 0.4 semver for CodeTracking
- add docs for break_on
- Revert "use compiled mode when there is no chance we will encounter a breakpoint"
- step through invokes
- add a missing method definition to docstring
- use compiled mode when there is no chance we will encounter a breakpoint
- fix what project is used when building builtins
- get rid of unused function
- Some pull requests not shown.
- Check nargs when extracting doc expressions
- make `show_backtrace` and `display_error` work for Frame
- Fix precompiles and enforce their validity
- ensure si doesn't step over anything
- step out of wrapper calls
- Step through preparation for kwarg calls
- Step through invokelatest
- Enhance the documentation
- fix accessing undef sparam
- An export-worthy API for break_on_error
- ensure we leave wrapper if we step to the end of it
- add functionality to step through macro expansion
- fix interpreting getting env vars on windows
- move builtin generation logic to precompilation time
- Implement core debug API here instead of Debugger.jl
- Debug commands: implement unwinding of stack on thrown exception
- Linked-list implementation
- add a function to extract local variables from a frame
- Add support for breakpoints (!)
- fixes for stack inversion in Debugger.jl, also remove some unused functions
Created an issue in JuliaLang/julia that received 10 comments
Confusing error message when returning an empty symbol
julia> eval(:($(Symbol("")))) ERROR: syntax: all-underscore identifier used as rvalue around REPL[30]:2 There is no all-underscore identifier used …
10
comments
- Show good backtraces on error
- Printing next expression can error for undefined variables
- Don't skip any initial stuff with `@run`
- Toggle code_lowered view and improve the printing of it
- Method signature is printed weirdly inside keyword calls
- Add a "floor" for source code printing
- Step out of wrapper functions
- Calling keyword functions look terrible
- Access to the error that caused us to break when break_on(:error) is enabled
- Breakpoint symbol looks bad in some terminals
- Unneccesary information printed when we hit a breakpoint
- Use the "export worthy" API for break on error
- Dedent source code when printing
- Toggle Compiled mode
- Unneccesary parenthesis around functions in "About to run:"
- Syntax highlighting
- BoundsError when trying to print source
- Ideas for an in debug mode interface to adding breakpoints
- Implement step out, stepping out of the current frame.
- Add resume / continue
- Add watch expressions
- Use TreeViews.jl to show variables
- Prevent stepping (and modifications) to a non top frame?
- Debugger stack and JuliaInterpreter stack grows in different directions.
- @interpreter^2 fails
- llvmcall with type parameters failure
- Number of arguments need to be checked for builtins
- Should :si not step through wrappers?
- Failure to step into closures?
- Temporary breakpoints
- New "build system" has a possible failure mode
- maybe_step_through_wrapper! can enter an infinite loop
- Step over macro expansions.
- `whereis` gives inconsistent file compared to `getfile` in macro expansions
- Binary builds cannot step into source code for stdlib functions due to bad location info
- Divergence between compiler and interpreter with logging macros
- Trying to breakpoint at file:line without Revise loaded says that file does not exist even if it does
- RFC: Allow access to the interpreter state from interpreted code
- Optimizing getfields should perhaps be a bit less aggressive.
- Chopped off docstring for whereis
- Keyword arguments in @interpret are not properly evaluated
- Stack is not empty after returning from top function with a try catch
- Doctests are failing
- Local variables are sometimes not updated
- Lack of newline after file info
- Some variables fail to define
- Pressing Ctrl + D spams iron> in the console
- Symbols and expressions need quoting when evaluating
- Difference between iron debugging and executing functions
- Breakpoint on lines doesnt seem to work properly?
- Absolute paths are needed for breakpoint on lines?
- SN doesn't seem to really work?
- Stepping into a Base function
- REPL functions crash the debugger
- Using a global const changes inlining behavior vs using a parameter
- Line number for first statement(s) in short form of function definition is wrong
- Mac nightly prints error when starting "could not load library "libcholmod""
- Stacktrace regression since display exception stacks
- feature request: implement error for overloading "final" methods