Plans for 64-bit support?

[Jeroen Walter]

Hi

Are there plans to support crashreports from 64-bit applications?
It seems a bit weird that this isn't implemented yet, as the crashreporter itself functions fine for 64bit applications.

Regards,

Jeroen

[Adrian Smith]

Hi Jeroen,

I have a working version running on windows that supports 64-bit however being unfamiliar with the codebase it required a substantial change. I replaced the crashdump reader & walker with its companion from the crashrpt system. This does mean the PDB cache is now depreciated since its now using the dbg library along with an external symbol store.

As such I am unsure how I would go about contributing these changes back to the community since you will lose some functionality.

-Adrian

[Jeroen Walter]

Hi Adrian,

I'm glad to here that it's at least possible :)
I'd prefer a version that doesn't need substantial code changes.
Using the dbg library as you did would also mean that the server is now limited to only 64bit crashes?
We want to use the server for both 32bit and 64bit crashes.
The loss of the PDB cache would not be a problem for us, we don't use that.
A very quick overview of the source code gave me the impression that it should not be so hard, but I can be severely wrong here.

We only need the functionality of creating collections and show the kind of exception, as we open the crashdumps in Visual Studio directly.
Unfortunatelly our development cycle doesn't allow for me to dig deep into this, so I'll have to postpone this issue.

[Jeroen Walter]

Hi

I've enabled 64-bit support by commenting out a few lines of code in CommandProcessor.cpp
In the method CCommandProcessor::DumpCrashReport comment out the following lines:


    if(pSysInfo && pSysInfo->m_uProcessorArchitecture != PROCESSOR_ARCHITECTURE_INTEL)
    {
        m_pLog->write(0, "Not supported CPU architecture of crash report file!\n");
        m_sErrorMsg = "Unsupported CPU architecture";
        goto cleanup;
    }

This will cause the 64bit reports to be ok for the crashfix server, so it can mark the reports as valid and make collections from them.
I don't know if the pdb functionality works for 64bit, but we don't use that as it's easier to download the crashdump and open it in Visual Studio.

[Dave Novak]

I too would like to see support for BOTH Win32 and Win64.  As to PDB cache being deprecated due to usage of external symbol store, I would think one could just as easily configure a local symbol store to which any uploaded PDBs could be added.  The dbg library would then be told to reference this symbol store.

It is quite unfortunate (surprising even) that CrashRpt supports both 32-bit and 64-bit but CrashSvr only supports 32-bit.  :(

[Jeroen Walter]

If you make the changes I suggested in the previous post, then you have 64bit support.
We've tested this on linux and on windows.
We did not test pdb support as we don't need it, but you can of course test this yourself.
It would be nice if the author of CrashFix server would incorporate these changes, but there's no reaction from him on this forum or on the sourceforge issue tracker :(
On the sourceforge issue tracker I've also posted some fixes for the webinterface, see https://sourceforge.net/p/crashfix/tickets/18/

[Hwan Min]

Hi Jeroen

I've applied your previous post and it works perfectly.
However it seems like CrashFix server cann't parse "call stack" properly from PDB file.
64bit dump only shows me like this "TestApp.exe + 0x4055ffff" even though 32bit dump has right call stack.
Did you check the 64bit dump call stacks?

[Jeroen Walter]

No, as stated in a previous post, we didn't test pdb functionality as we don't need it. We just open the dump and pdb in visual studio directly.

[Shuo Liu]

Hey Adrian,

Is there a chance you could share your version with 64-bit support, or at least share how it's done?

Thank you very much!


--
Shuo