You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
nim --debugger:native --lldb[:path/to/lldb] file.nim arg1 arg2 should compile and run via lldb -- app arg1 arg2 (likewise: --gdb[path/to/gdb] would compile and run via gdb specific syntax, ie: gdb --args app arg1 arg2
major
lldb should have Nim added as a language plugin; it should have bulk of it's logic written in Nim and be dlopen'd in lldb; see also [2]
calling code (eg via p mynimfun) via unmangled names should be supported
b mynimfun doesn't work
WORKAROUND: rbreak \bmynimfun_ (ie, regex) ; or b mynimfun[TAB] for auto-completion
stacktraces should show demangled names instead of mangled ones: * frame #0: 0x0000000100000dd8 app fun2_ALFlENhZsqTbOkwPqw67Tg_2 + 40 at ...
sample code showing how to write lldb plugins for nim (maybe wrapping around lldb's python plugin api)
lldb nim plugin should pretty-print variables correctly, eg:
(closing until I clean this up)
easy
nim --debugger:native --lldb[:path/to/lldb] file.nim arg1 arg2
should compile and run vialldb -- app arg1 arg2
(likewise:--gdb[path/to/gdb]
would compile and run via gdb specific syntax, ie:gdb --args app arg1 arg2
major
p mynimfun
) via unmangled names should be supportedb mynimfun
doesn't workWORKAROUND:
rbreak \bmynimfun_
(ie, regex) ; orb mynimfun[TAB]
for auto-completion* frame #0: 0x0000000100000dd8 app fun2_ALFlENhZsqTbOkwPqw67Tg_2 + 40 at ...
=> should show as
{ Sup = len=8, reserved = ..., data = "counter:" }
see related PR: Gdb pretty printers by krux02 · Pull Request #8263 · nim-lang/Nim
minor
--debugger:native
; docs should clarify this (includingnim --fullhelp | grep lldb
)lldb app
gives warning (for me, on OSX)ImportError: cannot import name _remove_dead_weakref
remove ENDB related code since it is deprecated in favor of gdb,lldb ; this'll cleanup nim a bitEDIT: endb can be revived, it's usefulmaybe related
error: expected expression
confusing error messages when using lines + --debugger:on fails with:error: expected expression
#7426related
env SHELL=/bin/bash gdb hello
(gdb) tui enable
The text was updated successfully, but these errors were encountered: