[Mono-bugs] [Bug 390788] New: Issues with Valgrind

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Thu May 15 09:54:10 EDT 2008


           Summary: Issues with Valgrind
           Product: Mono: Debugger
           Version: 1.9.0
          Platform: i686
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: cli
        AssignedTo: martin at novell.com
        ReportedBy: walker_643 at yahoo.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---

Created an attachment (id=215584)
 --> (https://bugzilla.novell.com/attachment.cgi?id=215584)
Valgrind Log for Test.exe

I use Valgrind quite a bit on each project before release. For C#/mono
projects, I find that Valgrind is not so useful primarily because it does not
give me good, clear information. Following the directions on the Mono-Project
site, I have called Valgrind with the proper parameters and suppression file.
This still does not give me info I can use. For example, consider the

---- test.cs ----
using System;
static class Program
    static void Main()
        Console.WriteLine("Hello world");
---- end test.cs ----

The assembly was then build with this:
mcs -debug -out:test.exe test.cs

I ran Valgrind on the resulting exe like so:
/usr/bin/valgrind --tool=memcheck -v --leak-check=full --log-file=vg.log
--smc-check=all --suppressions=/source/mono-1.9.1/mono.supp mono test.exe

I have attached the output file, vg.log, to this report. I think you will agree
that the contents of this file are not very useful, and maybe a little
misleading in places. My concerns are as follows:
1) Is it reasonable to expect to profile and/or leak-check a mono assembly
effectively with Valgrind? Does the quality of the output depend on the size or
complexity of the code?  If the answer to this question is that Valgrind is
simply not a good tool for use with mono assemblies, then we can stop here :)
2) Is the information on the Mono-Project web page out-of-date with the current
versions of Mono and Valgrind?
3) Consider this a blanket "what am I missing" question.

Both Mono and Valgrind are very well-developed, fundamental tools in their
respective corners. I hope there is a way for them to work together to help
refine our projects into tighter, cleaner, and safer code.


Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

More information about the mono-bugs mailing list