debugging a segfault in my rust programhttps://jvns.ca/blog/2017/12/23/segfault-debugging/ …
Unfortunately I think the only reason that fixed your segfault is because you're now leaking that memory indefinitely. If we ignore the "T must have the same size and alignment" line, your issue is that your third arg should be 560/80 not 560. It's in elem count not bytes
-
-
hmm i don't think i'm leaking the memory now?
-
The memory allocated by your vector is never freed. `slice` doesn't own its memory, and thus doesn't free it.
- 9 more replies
New conversation -
-
-
!! cool
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Wouldn't she catch the leak with Valgrind? Julia: did you run your fixed code through Valgrind?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.