Closed
Bug 508798
Opened 16 years ago
Closed 15 years ago
acceptance testsuite is not capturing assertion trace
Categories
(Tamarin Graveyard :: Tools, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: dschaffe, Assigned: dschaffe)
Details
Attachments
(1 file, 1 obsolete file)
504 bytes,
patch
|
brbaker
:
review+
|
Details | Diff | Splinter Review |
when running debug shells the acceptance test does no detect assertions triggered and fail the test. the contents of the assertion are not being output.
the reproducible testcase is with linux64, debug, 2329:d26a91a5ffd1
$ ./runtests.py mops/mops.as
...
FAILURES:
mops/mops.abc : unexpected exit code expected:0 actual:133 FAILED!
mops/mops.abc : captured output:
$ avmshell_d mops.abc_ mops.abc
Assertion failed: "Native instruction pointer overstep paging bounds; check overrideProtect for last instruction": _inExit ? containsPtr(exitStart, exitEnd, _nIns) : containsPtr(codeStart, codeEnd, _nIns) (/home/build/buildbot/tamarin-redux/linux64/tamarin-redux/nanojit/Assembler.cpp:322)
Trace/breakpoint trap
Perhaps the exit code 133 detection is happening before the assertion text. if exit code fails we should verbose print all output.
Flags: flashplayer-triage+
Assignee | ||
Comment 1•16 years ago
|
||
Assignee | ||
Comment 2•16 years ago
|
||
Attachment #393184 -
Attachment is obsolete: true
Attachment #393187 -
Flags: review?(brbaker)
Attachment #393184 -
Flags: review?(brbaker)
Updated•16 years ago
|
Attachment #393187 -
Flags: review?(brbaker) → review+
Assignee | ||
Comment 3•15 years ago
|
||
mark fixed.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•15 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•