Question about debugging issue related to GC

2021-12-26 Thread gcao
Thank you. I just tried Nim 1.6.0 and got same error. Traceback (most recent call last) /Users/gcao/proj/gene/src/genex/http.nim(268) init /Users/gcao/proj/gene/src/gene/interpreter_base.nim(172) eval /Users/gcao/proj/gene/src/gene/interpreter_base.nim(169) eval /Users

Question about debugging issue related to GC

2021-12-24 Thread Araq
> Based on the stack trace, there might be cyclic references. Run it through valgrind and ignore the stack traces and debuggers, they are highly ineffective tools when you cannot rule out some other unrelated memory corruptions elsewhere. Compile with `-d:useMalloc`.

Question about debugging issue related to GC

2021-12-24 Thread Yardanico
That seems like an actual ORC bug. Can you share the source code? Also, it might be worth testing on 1.6 as it has bug fixes for ARC/ORC.

Question about debugging issue related to GC

2021-12-24 Thread gcao
I have a native extension compiled as a dynamic library and loaded by the main program. In the native extension there is below code that causes SEGV while Nim is running GC for data allocated. The same code would run fine if put in the main program. discard VM.eval("(ns N)")