News for hackers. Stuff that matters.
Re:Pilotwings demos act differently depending on when the ca... by userbinator on Friday May 10, 2019 @10:45PM (#19884198)
There is a good debugging advice related to this story: "if your code is the same but suddenly starts behaving differently, check for hidden state."
Re:Pilotwings demos act differently depending on when the ca... by alanbernstein on Friday May 10, 2019 @11:45PM (#19884416)
It's more like code than state, isn't it? The thing that changed is the implementation of a circuit for computing the result of some calculation, i.e. a function.
Re:Pilotwings demos act differently depending on when the ca... by sgillen on Saturday May 11, 2019 @05:59AM (#19885440)
I very often think of the current definitions of functions as part of the program state.
Re:Pilotwings demos act differently depending on when the ca... by DDR0 on Saturday May 11, 2019 @01:39AM (#19884750)
You're right – but I don't think "hardware" usually counts as state!
Re:Pilotwings demos act differently depending on when the ca... by kibwen on Saturday May 11, 2019 @12:54PM (#19887105)
We don't generally count hardware as state because we expect it to be a reliable abstraction, but this same attitude applies to other things we do too: note that any program you've ever compiled can also count the compiler itself as state; this is the whole foundation for trusting-trust attacks!
Re:Pilotwings demos act differently depending on when the ca... by krz on Saturday May 11, 2019 @04:57AM (#19885292)
I usually say “check environment”, which is usually the reason — cron jobs run in non-interactive mode, new version of system library, wrong PATH variable, new math co-processor and so on.