Interesting forum question and answer

[Multicharacter]

Player question:
Does any of our crashes get logged? The reason I am asking is because when I play for example Planet Calypso and the game crashes, I get a "error report" containing data codes and stuff which I can choose to submit to the developers to help them track the problem.

I have never seen this in EQ2 upon a crash, so I wonder if this is even in the game? And if it is, is it hidden and working in the background all the time as we play? Because I don't think doing such is allowed without the user accepting it?


Rothgar answer:
Yes, we actually do log crashes when they occur on your client. Then, the next time you connect to the game, the crash is uploaded automatically. No personal information is sent with the crash report, just information about the game and things we would already know, like what IP address you are connecting from.

We review these crash logs almost daily and attack the top entries in the list since they are grouped by crash address.

If you want to PM me details about your specific crashes (IP Address, Computer Name, Time the Crash Occurred) I can look up those entries and see if they are something we are already working on, or something else.


I wonder if it would be wise to delete the crash logs whenever a crash is caused by ISXEQ2.

 

[Amadeus]

This IS very interesting. I never really considered that they would send the information on the next load (since most do it right when you crash.)

I wonder if it's the client sending the information, or the patcher.... I'll look into it though and see.

This would actually explain where I saw the code where the logs were generated, but dismissed it due to the fact that they didn't appear to be "sent" after being generated.

Do you have an example of a crash log that would be "sent" (as Rothgar mentioned?) If so, I'd like to see it ..even if it doesn't mention isxeq2 or innerspace.

 

[Multicharacter]

Yeah, I have an old eq2_crash.log from back when I got suspended (remember when we first learned using windbg to report crashes was no longer safe?). It doesn't specifically mention isxeq2.dll that I can see but it is filled to the brim with lines like this:
0x0018F71C: 0x03B72168, in C:\Program Files (x86)\InnerSpace\IS-Kernel.dll (0x03a30000)
0x0018F720: 0x0418DEE8
0x0018F724: 0x0018F738
0x0018F728: 0x03AE2691, in C:\Program Files (x86)\InnerSpace\IS-Kernel.dll (0x03a30000)

Can't send you PMs, but I'll try to find my IRC program and send you the full log. It's pretty long.