[Mono-dev] valgrind and mono

[Tom Hindle]

Hi Zoltan,

This improved things thanks.

still reports a: 
"Address 0x0 is not stack'd, malloc'd or (recently)"
but doesn't Kill itself now and continues.

Thanks
Tom


On Wed, 2009-09-02 at 03:15 +0200, Zoltan Varga wrote:
> Hi,
> 
>   Mono uses sigaltstack() to handle some signals, and valgrind is
> probably confused by
> that. Try configuring mono with --with-sigaltstack=no.
> 
>              Zoltan
> 
> On Wed, Sep 2, 2009 at 2:11 AM, Tom Hindle <tom_hindle at sil.org> wrote:
>         Hi,
>         
>         I understand from here http://mono-project.com/Debugging that
>         I should
>         be able to use valgrind with mono.
>         
>         However it seems to report stack corruption for simple handled
>         exceptions like this:
>         
>         try {
>                Control c = null;
>                c.Focus();
>         }
>         catch {
>         }
>         finally {
>         }
>         
>         valgrind reports:
>         ==14971==  Address 0x0 is not stack'd, malloc'd or (recently)
>         free'd
>         ==14971== Thread 1 return signal frame corrupted.  Killing
>         process.
>         
>         valgrind --tool=memcheck -v --leak-check=full --log-file=log
>         --smc-check=all --suppressions=mono.supp mono MyTest.exe
>         
>         
>         My valgrind is valgrind-3.4.1-Debian and my mono from svn is
>         r139201.
>         
>         Has anyone else experienced this?
>         
>         Any solutions / workarounds?
>         
>         Thanks
>         Tom
>         
>         
>         
>         _______________________________________________
>         Mono-devel-list mailing list
>         Mono-devel-list at lists.ximian.com
>         http://lists.ximian.com/mailman/listinfo/mono-devel-list
>