Crash error - how to obtain a detailed description ?

Welcome to our brand new Clickteam Community Hub! We hope you will enjoy using the new features, which we will be further expanding in the coming months.

A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.

Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!

Clickteam.

    Dear all,

    by running my application, I get a crash error which says only the event number where the error occurs.

    Question: is there any log file to read, in order to get more information about the error ? Or any way to get a more detailed description of what the cause was ?

    Thanks in advance,
    Sergio

    Please login to see this attachment.

    The line number should correspond to the line number in your frame events.

    Probably the crash occurs when executing the code on line 193 so you could look at the code on that line to see where the problem is.

    If your app jumps around a lot and doesn't run sequentially through the frame, you'd need to put in messages along the line: Debugger - Send Text to Output Window

    You'd be able to see what the last thing was that executed, and the next thing that should be executed will be what's causing the crash.

    Casual games: Please login to see this link.

    Thank you Janette, however I did already all that and I know where the problem is; but I need a detailed description, and I asked here, if there's a log file or a way to obtain more details. The problem is by deleting node connections by the APM ( Advanced Path Finding). I just need to know more details about, but probably there's no way to look in a log, probably because the APM is an extension.

    No, unless you have the debug symbols (PDB files), and a C++ debugger like Visual Studio or WinDbg, you won't get any more detail than an address that points to a bunch of assembly code.

    Darkwire Software Lead Programmer (C++ & C#)
    Please login to see this link. | Please login to see this link. | Please login to see this link. | Please login to see this link.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login