[Mono-dev] Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Mathieu Malaterre malat at debian.org
Wed Apr 6 12:23:51 UTC 2016


Hi all,

I am continuing my quest to understand what is going on with mono on
SMP PowerPC.

I am now looking at the gdb info produced, namely:

[...]
#19 0x10014c08 in mono_jit_runtime_invoke (method=0xf7de0018
<_rtld_global>, obj=0xffdba150, params=0xffdba1c0, exc=0x10014c08
<mono_jit_runtime_invoke+1204>, error=0x1068fe88) at
mini-runtime.c:2691
#20 0x101fec00 in mono_method_signature_checked (m=<error reading
variable: Cannot access memory at address 0x38>, error=<error reading
variable: Cannot access memory at address 0x3c>) at loader.c:2633
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================
[...]

This small value make it as if a bogus function pointer was passed.

Is there a way to confirm that this is the case (at compile and/or
runtime) within mono framework ?

thanks much for your guidance

-M


More information about the Mono-devel-list mailing list