As we're about to call into a function or start executing a script, the debugger hook is called with a frame containing a NULL pc. If that pc were instead initialized to the start of the script we were about to execute life would be easier for the debugger.
Brendan, I vaguely recall you were going to test for a null pc as a fix for some other debugger bug, I don't remember if that's the fix that went in, do you?
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.0
oops, meant to assigne this to myself.
Assignee: rogerl → rginda
Status: ASSIGNED → NEW
Comment on attachment 70706 [details] [diff] [review] patch Seems reasonable. r=shaver.
Attachment #70706 - Flags: review+
Comment on attachment 70706 [details] [diff] [review] patch The debugger can figure out this state and cope. We do not want to spend cycles here when the interpreter will get around to setting pc (if script), and at one point the GC needed to know that we were not yet interpreting. I don't think this is a good change for the core engine. Make the debugger pay the ?: or other random-logic cost. /be
Attachment #70706 - Flags: needs-work+
Status: NEW → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → INVALID
Marking Verified -
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.