Closed
Bug 266208
Opened 20 years ago
Closed 19 years ago
[@ js_PCToLineNumber] because of crash due to infinite recursion
Categories
(Other Applications Graveyard :: Venkman JS Debugger, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: timeless, Assigned: timeless)
Details
(Keywords: crash)
Crash Data
Attachments
(1 obsolete file)
js_PCToLineNumber(..., 0) JS_PCToLineNumber(..., 0) jsd_GetClosestLine(..., 0) jsdStackFrame::GetLine(...) I triggered infinite recursion in venkman the crash is because pc is null.
Attachment #163502 -
Flags: superreview?(brendan)
Attachment #163502 -
Flags: review?(rginda)
Comment 2•20 years ago
|
||
why is the pc null?
because venkman is trying to report the infinite recursion exception and there's nothing running. or something like that. unfortunately i killed the debugging session. i should be able to reproduce it...
Updated•20 years ago
|
Product: Core → Other Applications
Comment 4•19 years ago
|
||
Comment on attachment 163502 [details] [diff] [review] treat null pc as beginning of script r=rginda
Attachment #163502 -
Flags: review?(rginda) → review+
Comment 5•19 years ago
|
||
Comment on attachment 163502 [details] [diff] [review] treat null pc as beginning of script Null fp->pc means we haven't executed any ops in the frame's function or script yet, but we have entered the interpreter. The debugger hook can fire in this state. sr=me. /be
Attachment #163502 -
Flags: superreview?(brendan) → superreview+
Comment on attachment 163502 [details] [diff] [review] treat null pc as beginning of script mozilla/js/jsd/jsd_scpt.c 3.14
Attachment #163502 -
Attachment is obsolete: true
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Updated•13 years ago
|
Crash Signature: [@ js_PCToLineNumber]
Updated•6 years ago
|
Product: Other Applications → Other Applications Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•