[Mono-dev] Compiling Mono with debug symbols to diagnose an issue with embedded Mono

Jean-Michel.Perraud at csiro.au Jean-Michel.Perraud at csiro.au
Wed Aug 5 01:12:24 UTC 2015

I am trying to debug C code, mostly to step through the mono runtime itself. The issue seems to arise really quickly and I do not expect c# code (mine or the framework's) to be at fault here. That said, I would not at all refuse a howto guide for mixed mode (C and C#) debugging on Linux (not possible so far as I know). I may try to give a try on Windows with Visual Studio, but as a fallback option as this issue may not be reproducible on it anyway.
From: mono-devel-list-bounces at lists.ximian.com [mono-devel-list-bounces at lists.ximian.com] on behalf of Jonathan Mitchell [jonathan at mugginsoft.com]
Sent: Tuesday, August 04, 2015 7:34 PM
To: Mono-devel-list at lists.ximian.com
Subject: Re: [Mono-dev] Compiling Mono with debug symbols to diagnose an        issue with embedded Mono

> On 4 Aug 2015, at 08:26, Jean-Michel.Perraud at csiro.au wrote:
> * build/install mono from source (I know that) but with debug symbols
I would second this.

> * If the above is done, can I use MonoDevelop or other graphical front-end to attach to the process with embedded Mono and step through code with GDB. I can already attach  MonoDevelop to the R process and catch the crash, but the call stack is devoid of info and reference to the source code (presumably lacking the former debug symbols?)

Are you trying to debug the managed code or the embedded C API?


Mono-devel-list mailing list
Mono-devel-list at lists.ximian.com

More information about the Mono-devel-list mailing list