CrashFinder 2.55: A Bug Fix and x64 Support!

16 Comments July 5, 2006

Thanks to Dave Scherer who reported a problem in CrashFinder where the 32-bit version running on x64 wasn't properly handling the WOW64 version of NTDLL.DLL because it is missing the import table. In doing the fix I figured it was the time to produce an x64 version of CrashFinder. Download the code here. As always, let me know if you find a problem. My mail address is 'john' at this company.


16 Comments

  • Gravatar Image
    Mike Diack July 18, 2006 2:36 PM

    Hi John, Was the lint output I sent you of some possible memory management issues in Crashfinder 2.55 of use? By the way, did you know that this web page doesn't render correctly in Firefox 1.5.0.4? Mike

  • Gravatar Image
    David J Hughes April 24, 2007 11:02 AM

    I was looking for the updated version of this much love tool. Thanks!

  • Gravatar Image
    bingfeng April 28, 2007 11:10 PM

    Hi john,

    thanks for your excellent tool at first!

    I downloaded you new release and compiled it on my XP SP2 machine, the IDE is VS2005 and I also have the lastest SDK installed. but unfortunately the result cannot work at all! i traced it and found that when I want to open a .exe, a call to SymGetModuleInfo64 failed with the error code 67(The parameter is incorrect.) I want to know what's up and how to work out it.

    If you need more information, please contact bingfeng.zhao (at) ca.com.

    Thanks

  • Gravatar Image
    bingfeng April 29, 2007 5:01 AM

    I'd like add some another info.
    when I try to open a .exe(the OpenFile dialog don't show still), the call to SymGetModuleInfo64 failed with error 203 (The system could not find the environment option that was entered), and the next call to that API return above post mentioned error.
    BYW, My machinie is under a domain-controled environment, and my login user belongs to administrator group.

  • Gravatar Image
    bingfeng April 29, 2007 5:08 AM

    Sorry for my mistake!
    I set many breakpoints and its make me somewhat mad:( I withdraw the last post, it's just OK.

  • Gravatar Image
    Rajesh July 12, 2007 9:56 AM

    Need the software crash finder

  • Gravatar Image
    Cees November 16, 2007 3:53 PM

    I'm changing from VC98 to VS8 and I have troubles keeping the good old Petzold development method working. Never used Visual and try to keep it that way, but MAPINFO:LINES was heaven for any crash could be handled. Microsoft like they try to eliminate any competion! I think this crashfinder is heavon on earth. Keep on doing the good work!

  • Gravatar Image
    Anonymous November 23, 2007 2:12 PM

    Hi,

    I try to compile CrashFinder_2.55 on vs2005. It passed comipler, but
    there is assertion when running it. The question is that does it run with vs2005 ?

    thanks,
    Park

  • Gravatar Image
    Jim April 22, 2008 3:44 PM

    Dowloading crashfinder

  • Gravatar Image
    Jooyoung July 25, 2008 1:23 AM

    Thankyou!
    You had good job.

  • Gravatar Image
    Jooyoung July 25, 2008 1:25 AM

    WoW
    You had a good job.

  • Gravatar Image
    Sekhar Samala September 16, 2008 10:52 AM

    I need this tool to find crash function using address

  • Gravatar Image
    Chris Reed September 22, 2008 5:38 AM

    It looks like it reads the addresses into a DWORD (32 bit), truncating down to 32 bit. I've got a fix if anyone's interested.

  • Gravatar Image
    Bernd Giesen October 28, 2008 3:43 AM

    John, the bug reported by bingfeng dated from April 28th, 2007 seems not to be solved at all until today. I still ran into the same trouble when building the binary under VS2003 from the provided sources. However, GetLastError() reports error 87 here after calling ::SymGetModuleInfo64 (not 67 as stated by bingfeng), which indeed means 'The parameter is incorrect'. Will you still provide a fix for this issue in the near future? I really don't wanna miss this excellent tool!

  • Gravatar Image
    jrobbins October 31, 2008 1:54 PM

    Bernd,

    You don't have the latest version of DBGHELP.DLL and SYMSRV.DLL in the same directory as CrashFinder.EXE. Copy those two DLLs from your Debugging Tools for Windows (WinDBG) install and you'll be set.

    John Robbins

  • Gravatar Image
    songmin April 26, 2010 10:42 PM

    thanks

Have a Comment?

Archives