Gendarme Issue with Sonar

[Donald]

Hi,

I originally sent this to the Sonar mailing list but think that
putting it here might help too:

I am currently receiving some issues when running Sonar against a .NET
project. The solution that I’m running it against is large (100+
projects) and there is 1 project in particular which is hanging the
Gendarme analysis when run via Sonar. I have reduced the solution
down to contain only this 1 project but the Gendarme process is still
hanging, it sits with constant memory (between 60 – 100mb) and around
50-60% CPU usage. There is minimal disk and memory access, it looks
like the process has just hung.

I also have another similar issue with a different project in a
separate solution. When running Gendarme against this I receive a
NullReferenceException:

Caused by: org.sonar.dotnet.tools.gendarme.GendarmeException: Gendarme
analysis
failed: execution was interrupted by a non-handled exception. This is
likely a b
ug inside Gendarme and should be reported on Novell's bugzilla (http://
bugzilla.
novell.com) or on the mailing-list.
at
org.sonar.dotnet.tools.gendarme.GendarmeRunner.execute(GendarmeRunner
.java:124)
at
org.sonar.plugins.csharp.gendarme.GendarmeSensor.launchGendarme(Genda
rmeSensor.java:153)
at
org.sonar.plugins.csharp.gendarme.GendarmeSensor.analyse(GendarmeSens
or.java:107)

However I don’t receive any errors and it doesn’t hang when I run the
Gendarme analysis via the Gendarme Wizard. Does anyone know what can
cause this issue? What does Sonar do differently with the Gendarme
process that the Gendarme Wizard doesn’t do? Any suggestions would be
much appreciated as this is driving me crazy!

Both projects are .NET 4 class libraries and I have received both
errors with Sonar 3.0.1 (with C-Sharp Plugin Ecosystem version 1.3)
and 2.13.1 (with C-Sharp Plugin Ecosystem version 1.2). I’m running
Gendarme version 2.11. I have tried this on both a Windows 7 64-bit
and a Windows Server 2008 r2 server.

Thanks,

[Donald]

I'd like to update this and it looks like Gendarme is hanging when I'm
running it via the command line on the same dlls, what happens
differently when running via command line as to using the wizard?

I'm running

"gendarme --v C:\MyAssembly.dll"

All that I see is:

"Initialization: 0.7 seconds
MyAssembly.dll"

and then it hangs, CPU usage stays at around 50%. However when I run
this same dll via the CommandPrompt it takes ~20seconds.

Any suggestions?

[Sebastien Pouliot]

On Tue, May 15, 2012 at 8:48 AM, Donald <mrdona...@gmail.com> wrote:
> I'd like to update this and it looks like Gendarme is hanging when I'm
> running it via the command line on the same dlls, what happens
> differently when running via command line as to using the wizard?
>
> I'm running
>
> "gendarme --v C:\MyAssembly.dll"
>
> All that I see is:
>
> "Initialization: 0.7 seconds
> MyAssembly.dll"
>
> and then it hangs, CPU usage stays at around 50%.  However when I run
> this same dll via the CommandPrompt it takes ~20seconds.
>
> Any suggestions?

It should be identical. However your PATH might differ in your command
prompt so this might affect how assemblies can be resolved. However it
should not hang.

> --
> You received this message because you are subscribed to the Google Groups "Gendarme" group.
> To post to this group, send email to gend...@googlegroups.com.
> To unsubscribe from this group, send email to gendarme+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/gendarme?hl=en.
>