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

[Rodrigo Kumpera]

This is caused because your mono was built with a bad TLS model and the
runtime is unable to find
the required offset.

Rebuild it using --with-tls=pthread should workaround your issue until
someone figures out what's wrong with
your setup.

On mixed mode debugging. It's incredibly complicated and there are no plans
to support it in the immediate future.

--
Rodrigo




On Tue, Aug 4, 2015 at 3:26 AM, <Jean-Michel.Perraud at csiro.au> wrote:

> I have an R package with embedded Mono, on Linux, that is working on Mono
> 3.12.x series but broken since  Mono 4.0.x.
> Crashes with:
>     Assertion at sgen-alloc.c:774, condition `tlab_next_addr_offset != -1'
> not met
>
> Repro and details at https://github.com/jmp75/rClr/issues/7, but optional
> for this present question.
>
> What I am after is to step in debug mode through Mono, to diagnose and
> hopefully figure out a fix, but could not find a procedure to:
>
> * build/install mono from source (I know that) but with debug symbols
> * 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?)
>
> Any advice on how to go about it is welcome. I hope we can do better than
> command line gdb.
>
> Cheers
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20150807/9a26f57f/attachment.html>