Exception Thrown When Running From Command Line
darryl_staflund
Posts: 4
Hi Red Gate,
Congratulations on the release of Exception Hunter. It looks like a great product and is really quite innovative -- I haven't heard of a similar tool.
I tried running Exception Handler from the command-line on an application I am developing and received the following exception (NB: Here's the command-line output of my run):
Other than this particular exception, I have been able to run Exception Hunter no problem.
Darryl
Congratulations on the release of Exception Hunter. It looks like a great product and is really quite innovative -- I haven't heard of a similar tool.
I tried running Exception Handler from the command-line on an application I am developing and received the following exception (NB: Here's the command-line output of my run):
C:\Work\wm\build>"c:\Program Files\Red Gate\Exception Hunter 1\Hunt.exe" /assembly:".\<MyAppHere>.exe" /all /warnOnlyOnMissingReference:on Exception Hunter Command Line V1.0.0.551 ====================================================================================================================================================================================================== Copyright c Red Gate Software Ltd 2007 = Loading .NET framework = Loading assemblies Warning: Could not locate assembly ActiveReports.Chart, Version=4.1.0.1127, Culture=neutral, PublicKeyToken=cc4967777c49a3ff = Calculating exceptions Error: Unhandled exception: Could not analyse the method NativeOledbWrapper::MemoryCompare due to an exception. *** Inner Exception: The method or operation is not implemented. (NotImplementedException) at bm.get_Flags() at aK.ModelDataFlow(W dataState) at g.a(Int32 , X , c , Boolean ) at g.d() at g.c() at e.a() *** Inner Exception: Could not analyse the method NativeOledbWrapper::MemoryCompare due to an exception. (CouldNotAnalyseMethodException) at e.a() at e.c() at e.a(C ) at bw.CalculateExceptionsThrownByMethod(IClassMethod method) at c.PerformAnalysis() at RedGate.ExceptionHunter.CommandLine.CommandLine.a(String[] ) C:\Work\wm\build>
Other than this particular exception, I have been able to run Exception Hunter no problem.
Darryl
Comments
We have identified a potential problem in the handling of missing dependent assemblies in the command-line version of Exception Hunter, which will be fixed in a future release.
In the meantime, the program should work without error if you specify the path to the missing assembly in the searchPaths argument: We're sorry for the inconvenience.
BTW, this is the full line I'm currently executing (I've got another one with bin\debug paths to every reference in the project, separated by commas):
C:\DEV2\LOSSMIT\WebSite\bin>"C:\Program Files\Red Gate\Exception Hunter1\Hunt.exe" /assembly:elmsbl.dll /all /warnOnlyOnMissingReference:on /searchPaths:"C:\Program Files\Microsoft Visual Studio 8\ReportViewer","C:\dev2\LossMit\WebSite\bin" /exceptionReport:true
You may want to try the latest private build of Exception Hunter 1.1. It has some improved reading of assembly metadata:
http://downloads.red-gate.com/BleedingE ... tBuild.msi
If you can't analyze a method, it may just be that the assembly, or one of its' dependencies, was built using an obfuscator. These can make it difficult or impossible for Exception Hunter to disassemble the code (essectially that's their job!) and there may not be a way of analyzing this dll without getting a version that isn't obfuscated.