Re:How a 20 year old bug in GTA San Andreas surfaced in Wind...
by frollogaston on Wednesday April 23, 2025 @04:27PM
(#43776311)
Randomization at this level would be too expensive. There are tools that do this for debug purposes, and your stuff runs a lot slower in that mode.
[ Parent
| on HN ]
Re:How a 20 year old bug in GTA San Andreas surfaced in Wind...
by foxhill on Wednesday April 23, 2025 @05:02PM
(#43776596)
it probably shouldn’t be a “release” thing. actually, certainly. i do wonder how many bugs would never have seen the light of day, if someone’s “set” actually turned out to be a sequence (i.e. allowed duplicate values) resulting in a debug build raising an assert.
Re:How a 20 year old bug in GTA San Andreas surfaced in Wind...
by Arainach on Wednesday April 23, 2025 @08:36PM
(#43778199)
Debug builds are worthless for catching issues. How many people actually run them? Perhaps developers run debug builds of individual binaries they're working on when they're trying to repro a bug, but my experience at every company of every size and position in the stack (including the Windows team) is that no one does their general purpose use on a debug build.
Re:How a 20 year old bug in GTA San Andreas surfaced in Wind...
by dontlaugh on Wednesday April 23, 2025 @10:03PM
(#43778618)
Especially in games, it’s common for only the highly optimised release builds to have playable performance.
Re:How a 20 year old bug in GTA San Andreas surfaced in Wind...
by frollogaston on Thursday April 24, 2025 @12:37PM
(#43784699)
Yeah, even their integration tests will probably run in opt mode.
Re:How a 20 year old bug in GTA San Andreas surfaced in Wind...
by throwaway2037 on Wednesday April 23, 2025 @10:55PM
(#43778874)
I had to Google to find the tid bit that I read about Perl years ago. I think this will affect iteration order of dicts.
> Nov 22, 2012 — Perl 5.18 will introduce per process hash randomization and almost certainly will feature a new hash function.