[Mono-dev] debug help on mono runtime

Vlad Brezae vlbrez at microsoft.com
Tue Oct 18 20:58:14 UTC 2016


    You can call mono_pmip (ip) or mono_print_method_from_ip (ip). For going deeper,  you can either unwind the stack manually looking for the return ip’s on the stack (which will be similar to 0x40013eca), or call mono_print_thread_dump (0)


From: Mono-devel-list <mono-devel-list-bounces at lists.dot.net> on behalf of M Jam <mjam.mono at gmail.com>
Date: Tuesday, 18 October 2016 at 22:08
To: "mono-devel-list at lists.dot.net" <mono-devel-list at lists.dot.net>
Subject: [Mono-dev] debug help on mono runtime

Hi all,

If I at a point where I see something like this (gdb) bt
#0 ves_icall_System_IO_MonoIO_Write (handle=<optimized out>, src=<optimized out>, src_offset=<optimized out>, count=<optimized out>, error=<optimized out>) at file-io.c:895
#1 0x0000000040013eca in ?? ()
#2 0x0000000000000006 in ?? ()
#3 0x00007ffff6803ce0 in ?? ()
#4 0x00007ffff6805668 in ?? ()
#5 0x0000000000000000 in ?? ()

How do I know who is calling ves_icall_System_IO_MonoIO_Write()?
Is there a way to know who is calling from address 0x0000000040013eca?

M Jam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dot.net/pipermail/mono-devel-list/attachments/20161018/096b21bc/attachment.html>

More information about the Mono-devel-list mailing list