2 ms·
https://news.ycombinator.com/item?id=33287817 https://news.ycombinator.com/item?id=33287817 You bet I have! What would you like to know beyond that comment?
by girvo 4y ago
https://news.ycombinator.com/item?id=33287817 https://news.ycombinator.com/item?id=33287817
You bet I have! What would you like to know beyond that comment?
- generichuman 4y agoWhat's your debugging experience like? i.e. The tools you use, do you have to debug the C output, etc.
- girvo 4y agoBecause I live in embedded land, I use the compileOnly C output. What’s really nice about that though is with debugger:native enabled, it embeds source-map comments in the C back to the Nim lines they tie to! All in VSCode with gdb (and OpenOCD). This gives me full interactive debugging, breakpoints etc of the Nim source directly — including via a JTAG from the ESP32 itself :) it’s super nice, considering none of the tools internally were built for Nim haha. The #Line macro is surprisingly powerful in C debugging land it turns out If you’re doing desktop/non embedded stuff it’s even easier, and you can also enable useMalloc and run Nim programs through the Valgrind suite easily