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?
"gendarme --v C:\MyAssembly.dll"
All that I see is:
"Initialization: 0.7 seconds
and then it hangs, CPU usage stays at around 50%. However when I run
this same dll via the CommandPrompt it takes ~20seconds.
On May 14, 4:17 pm, Donald <mrdonaldg...@gmail.com> wrote:
> 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
> Caused by: org.sonar.dotnet.tools.gendarme.GendarmeException: Gendarme
> 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://
> novell.com) or on the mailing-list.
> 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.