|
From: | Gregory Heytings |
Subject: | bug#61504: 29.0.60; executing byte-code from previous build causes SIGSEGV crash |
Date: | Tue, 14 Feb 2023 20:47:28 +0000 |
By the way, doesn't the patch switch the restoration order of narrowing and restriction, respectively? Maybe it doesn't matter?Hmmm, that's a good question! The evaluation order of parameters is unspecified in C,The problem is not in the evaluation order of params in `save_restriction_save` (this order doesn't matter because the code is pure), it's in `save_restriction_restore`.
Indeed, I initially misunderstood what Mattias said, but after reading it again I got it. This is now fixed.
Thanks!
[Prev in Thread] | Current Thread | [Next in Thread] |