If you need to examine a large set of execution sequences, a debugger
wouldn't really help. I think you want a custom evaluator written to
explore exhaustively the space of possible context switches (e.g., via
backtracking).
Greg
On Wed, Jan 19, 2011 at 4:26 PM, Mark Engelberg
wrote:
> Hmm, I d
Anyone up for a dissertation? Multi-stepping debugging is, eh, pushing it.
On Jan 19, 2011, at 2:43 PM, Doug Orleans wrote:
> The following program was a puzzle in the 2011 MIT Mystery Hunt held last
> weekend. (I'm not linking directly to the site because they posted a
> solution and I
Hmm, I don't think the greedy approach will work.
The first line of the second thread, (set! a (list c)), will execute
without error immediately, but it really needs to happen between the
evaluation of a and (first a) in the first line of the first thread.
Probably needs to be done by hand.
_
It looks like the puzzle is to find an interleaving of execution that
makes sense.
Other than solving it by hand, one idea I have is to wrap around each
line of code some sort of error handler that keeps trying that line
until it succeeds. This should work if the puzzle has been designed
so that
The following program was a puzzle in the 2011 MIT Mystery Hunt held last
weekend. (I'm not linking directly to the site because they posted a
solution and I don't want you to be tempted to look at the answer
prematurely...) I was disappointed that Dr Racket doesn't seem to have a
multi-threaded
5 matches
Mail list logo
