Overwriting process global when recording in browser and replaying under node

[msridhar]

Consider the following code:

if (typeof process !== "undefined") {
  console.log("foo");
} else {
  console.log("baz");
}

Say we record the above script in the browser, and then replay under node.js. In the browser, process is undefined, so this gets recorded to the trace. During replay, we read in the trace and overwrite the real process global with undefined, which seems bad. While replay itself seems to proceed, replay.js reads process at the end, which causes a crash.

Not sure of the right fix for this one. Maybe replay.js should stash away a pointer to the process object before starting actual replay?

[msridhar]

Actually, stashing away the pointer in replay.js is insufficient; all analyses (and dependent libraries) that refer to process would have to do something different, which seems impossible to enforce.