mono-symbolicate issues

JoeProJoePro CAUniversity ✭✭✭

Hi,

I'm having a hard time using mono-symbolicate.
It always spits out this message on the first line of the stack trace:
Warning: MVID directory does not exist:

And then crashes with this exception:
Unhandled Exception:
System.Exception: Could not find data for method token 6000C1A
at Mono.SeqPointInfo.GetILOffset (System.Int32 methodToken, System.UInt32 methodIndex, System.Int32 nativeOffset) [0x00028] in <282f562230e2413297d612f94f82a6b7>:0
at Mono.AssemblyLocationProvider.TryResolveLocation (Mono.StackFrameData sfData, Mono.SeqPointInfo seqPointInfo) [0x001c9] in <282f562230e2413297d612f94f82a6b7>:0
at Mono.SymbolManager.TryResolveLocation (Mono.StackFrameData sfData) [0x0003b] in <282f562230e2413297d612f94f82a6b7>:0
at Mono.Symbolicate.SymbolicateAction (System.Collections.Generic.List1[T] args) [0x00034] in <282f562230e2413297d612f94f82a6b7>:0 at Mono.Symbolicate.Main (System.String[] args) [0x0017f] in <282f562230e2413297d612f94f82a6b7>:0 [ERROR] FATAL UNHANDLED EXCEPTION: System.Exception: Could not find data for method token 6000C1A at Mono.SeqPointInfo.GetILOffset (System.Int32 methodToken, System.UInt32 methodIndex, System.Int32 nativeOffset) [0x00028] in <282f562230e2413297d612f94f82a6b7>:0 at Mono.AssemblyLocationProvider.TryResolveLocation (Mono.StackFrameData sfData, Mono.SeqPointInfo seqPointInfo) [0x001c9] in <282f562230e2413297d612f94f82a6b7>:0 at Mono.SymbolManager.TryResolveLocation (Mono.StackFrameData sfData) [0x0003b] in <282f562230e2413297d612f94f82a6b7>:0 at Mono.Symbolicate.SymbolicateAction (System.Collections.Generic.List1[T] args) [0x00034] in <282f562230e2413297d612f94f82a6b7>:0
at Mono.Symbolicate.Main (System.String[] args) [0x0017f] in <282f562230e2413297d612f94f82a6b7>:0

Any idea what's going on here? I'm on the latest version of Xamarin.iOS and VS4Mac. The mSYM folder exists and contains tons of subfolders - just not the one(s) it's looking for.

Initially, I thought I was using the wrong mSYM folder, but it's the same as the one included in the archive I built.

Posts

  • JoeProJoePro CAUniversity ✭✭✭

    @RolfBjarneKvinge Am I using this wrong? There doesn't seem to be a whole lot of documentation on this tool - which is surprising because this information is very useful to have when debugging in issue in production.

  • AndrejSpilakAndrejSpilak SIMember
    edited November 2017

    @JoePro see forums.xamarin.com/discussion/105183/catching-line-numbers-on-exceptions. The paths provided are for windows machine, but still it might help you.

    Sorry because the site is not linked, obviously I'm not around for enough time to have permission to post links (if even they are internal!!)

  • JoeProJoePro CAUniversity ✭✭✭

    Thanks @AndrejSpilak
    Looks like this might be an issue with my setting - I will run more tests.

Sign In or Register to comment.