Closed Bug 659233 Opened 9 years ago Closed 9 years ago

TI: "Assertion failure: loop == code->loop," with trap

Categories

(Core :: JavaScript Engine, defect, critical)

x86
macOS
defect
Not set
critical

Tracking

()

RESOLVED FIXED

People

(Reporter: gkw, Unassigned)

References

(Blocks 2 open bugs)

Details

(Keywords: assertion, testcase)

f = (function() {
    while (h) {
        continue
    }
})
dis(f)
trap(f, 0, '');
f()

asserts js debug shell on JM changeset 29f08848d96c with -m, -a, -d and -n at Assertion failure: loop == code->loop,

flags: LAMBDA NULL_CLOSURE
off     op
-----   --
main:
00000:  goto 10 (10)     <-- trap goes here
00003:  trace 0
00006:  goto 0 (-6)
00009:  nullblockchain
00010:  getgname "h"
00015:  ifne 3 (-12)
00018:  stop

Source notes:
 ofs  line    pc  delta desc     args
---- ---- ----- ------ -------- ------
  0:    1     0 [   0] newline 
  1:    2     0 [   0] while    offset 15
  3:    2     3 [   3] while    offset 12
  5:    2     6 [   3] newline 
  6:    3     6 [   0] continue
  7:    3    10 [   4] setline  lineno 2
  9:    2    18 [   8] xdelta  
 10:    2    18 [   0] setline  lineno 4
Fix trap handling.  Is it possible for a trap to actually be added by the debugger here?

http://hg.mozilla.org/projects/jaegermonkey/rev/79746474b25a
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.