Miraculously, just as all hope seemed lost, I discovered that
ahead-of-time indeed causes a crash, but before the crash a shared
object file is written containing the compiled code. The presence of
this shared object file apparently causes function call information to
appear in stacktraces (when
On Thu, Oct 4, 2012 at 1:40 PM, Tom Hughes t...@compton.nu wrote:
The mono_jit_runtime_invoke is a big clue - those will be run time
generated code that the JIT has created so they won't be in the symbol table.
Ah, that makes a lot more sense than my theory.
On Thu, Oct 4, 2012 at 1:50 PM,
On Tue, 2012-10-09 at 11:40 -0500, Kerrick Staley wrote:
Otherwise, you might always try using gdb/vgdb to connect to the process
under Valgrind when the error is raised : gdb might maybe help
to see what is going on.
You mean I should use --db-attach=yes (as Greg suggested)?
Since