"Lockdown" Error Code 38 data gathering.

Well what gets me is the GM that responded regarding the CS ticket originally offered to log on to my account to "check something". When I got locked out yesterday, I responded with, well, here it is exactly;

-snip-

So, from my understanding of what Borsham said, they have tried to log into the affected accounts and couldn't, and that's it?! Sigh, this does not make me feel good. :/

They are idiots.
Not being able to log onto the character is replicating the error.
But it's not something a GM/CS agent should do. It's something a developer (programmer) should do, while running a debug-enabled client.

 How debugging crashes works

When said client crashes, as expected, the developer can use debug information - the line of code at which the crash occurred, the call stack, and the values of various variables - to see just what "file" had its "end" reached.
Often with cases of memory corruption, like these, it's not immediately obvious at what point the corruption occurrs, and so the programmer would have to set breakpoints in the program and tell the debugger to track changes to certain variables, and then run the client again and try to log on to the affected character. They would be doing this over and over again, until they discover at what point things get written where they shouldn't.
It's not an easy type of bug to find and fix, but it's doable, and having an affected character to try it with is key.

As with the Error 38 on cash shop 3 years ago, this really makes me wish I could get my hands on a debug client.