Do I understand correctly that we don't keep the debugging symbol files (.PDB files) for each version of Allegiance that is released?
So when someone is playing and their client crashes, how do we debug what went wrong? Is the answer to that "we don't, because we throw away / never generated the only file that could possible help us figure out what happened?" I hope not.
I mean, I just watched Metz spend the whole day trying to figure out why his high-res map pack was causing crashes on some machines and not others. And while it warms the cockles of my heart to see his time wasted like that, if it really is the case that the only way to debug these things is by trial and error and by coincidence, that is really, really bad.
Yes, release binaries have optimizations turned on and that might make interpreting the dump a bit tricky, but at least the call stack will be right and the IP will be somewhere in the general area, and chances are all he would have to do was just email me the dump and there's a good chance I could tell you that not only is it a problem in Cort UI, I could tell you probably what is wrong with Cort UI and how it could be fixed.
Debugging symbols?
Last edited by cashto on Wed May 21, 2014 4:30 am, edited 1 time in total.
Globemaster_III wrote:QUOTE (Globemaster_III @ Jan 11 2018, 11:27 PM) as you know i think very little of cashto, cashto alway a flying low pilot, he alway flying a trainer airplane and he rented
Doesn't seem to be CortUI, now.
I was having endless crashes until I got rid of CortUI. Then it was fine.
Until a while later when I started getting plagued with crashes again.
It's pretty $#@!ing hard to isolate seemingly random crashes with just trial and error.
I've spent 2 days on this now.
and crashed Mach, CSS, and TestUS1 today.
I was having endless crashes until I got rid of CortUI. Then it was fine.
Until a while later when I started getting plagued with crashes again.
It's pretty $#@!ing hard to isolate seemingly random crashes with just trial and error.
I've spent 2 days on this now.
and crashed Mach, CSS, and TestUS1 today.
Last edited by Mastametz on Wed May 21, 2014 6:45 am, edited 1 time in total.
There's a new sheriff in town.
Oh hey, look what I found: http://acss.alleg.net/downloads/AllegiancePDB.zip
Looks like it matches the current allegiance binary, too.
Masta, I think you should have a directory on your machine: c:\users\<username>\AppData\Local\CrashDumps. In there, you should see some .dmp files. If that's the case, copy the allegiance* ones somewhere that I can find them.
Looks like it matches the current allegiance binary, too.
Masta, I think you should have a directory on your machine: c:\users\<username>\AppData\Local\CrashDumps. In there, you should see some .dmp files. If that's the case, copy the allegiance* ones somewhere that I can find them.
Globemaster_III wrote:QUOTE (Globemaster_III @ Jan 11 2018, 11:27 PM) as you know i think very little of cashto, cashto alway a flying low pilot, he alway flying a trainer airplane and he rented
stack traces from that pdb dont seem to be correct
These bugs haven't been fixed yet because don't have any developers interested in fixing them up. --Tigereye
Imago's stupid-sensor is supersensitive. --RealPandemonium
The art is managing the flow of the drama to achieve the desired results. --Big_Beta_Tester
joeld wrote:But we’ve been amazed at the level to which some of the Allegiance fans have remained hard-core.