Closed Bug 590550 Opened 15 years ago Closed 14 years ago

valgrind SIGILL on some acceptance tests

Categories

(Tamarin Graveyard :: Tools, defect)

Product:
Tamarin Graveyard
Component:
Tools
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED INVALID

People

(Reporter: treilly, Unassigned)

References

Details

as3/Definitions/Function/functionReturnTypes.abc : unexpected exit code expected:0 actual:-4 Signal Name: SIGILL FAILED! ecma3/Expressions/e11_5_1.abc : unexpected exit code expected:0 actual:-4 Signal Name: SIGILL FAILED! ecma3/Expressions/e11_5_2.abc : unexpected exit code expected:0 actual:-4 Signal Name: SIGILL FAILED! ecma3/Expressions/e11_5_3.abc : unexpected exit code expected:0 actual:-4 Signal Name: SIGILL FAILED! ecma3/Math/e15_8_2_1.abc : unexpected exit code expected:0 actual:-4 Signal Name: SIGILL FAILED! ecma3/Number/e15_7_3_3_1.abc : unexpected exit code expected:0 actual:-4 Signal Name: SIGILL FAILED! ecma3/Number/e15_7_3_3_2.abc : unexpected exit code expected:0 actual:-4 Signal Name: SIGILL FAILED! ecma3/Number/e15_7_3_3_3.abc : unexpected exit code expected:0 actual:-4 Signal Name: SIGILL FAILED! ecma3/Number/e15_7_4_7_1.abc : unexpected exit code expected:0 actual:-4 Signal Name: SIGILL FAILED! ecma3/ObjectObjects/e15_2_1_1_rt.abc : unexpected exit code expected:0 actual:-4 Signal Name: SIGILL FAILED! ecma3/TypeConversion/e9_3.abc : unexpected exit code expected:0 actual:-4 Signal Name: SIGILL FAILED! ecma3/TypeConversion/e9_9_1_rt.abc : unexpected exit code expected:0 actual:-4 Signal Name: SIGILL FAILED! ecma3/Types/e8_5.abc : unexpected exit code expected:0 actual:-4 Signal Name: SIGILL FAILED! results.txt:3154: ecma3/Number/e15_7_3_3_1.abc : unexpected exit code expected:0 actual:-4 Signal Name: SIGILL FAILED! results.txt:3156: ecma3/Number/e15_7_3_3_2.abc : unexpected exit code expected:0 actual:-4 Signal Name: SIGILL FAILED! results.txt:3158: ecma3/Number/e15_7_3_3_3.abc : unexpected exit code expected:0 actual:-4 Signal Name: SIGILL FAILED! results.txt:3160: ecma3/Number/e15_7_4_7_1.abc : unexpected exit code expected:0 actual:-4 Signal Name: SIGILL FAILED! results.txt:3162: ecma3/ObjectObjects/e15_2_1_1_rt.abc : unexpected exit code expected:0 actual:-4 Signal Name: SIGILL FAILED! results.txt:3190: ecma3/TypeConversion/e9_3.abc : unexpected exit code expected:0 actual:-4 Signal Name: SIGILL FAILED! results.txt:3192: ecma3/TypeConversion/e9_9_1_rt.abc : unexpected exit code expected:0 actual:-4 Signal Name: SIGILL FAILED! results.txt:3194: ecma3/Types/e8_5.abc : unexpected exit code expected:0 actual:-4 Signal Name: SIGILL FAILED! vex x86->IR: unhandled instruction bytes: 0x66 0xF 0xBF 0x44 ==87960== valgrind: Unrecognised instruction at address 0x303dab. ==87960== Your program just tried to execute an instruction that Valgrind ==87960== did not recognise. There are two possible reasons for this. ==87960== 1. Your program has a bug and erroneously jumped to a non-code ==87960== location. If you are running Memcheck and you just saw a ==87960== warning about a bad jump, it's probably your program's fault. ==87960== 2. The instruction is legitimate but Valgrind doesn't handle it, ==87960== i.e. it's Valgrind's fault. If you think this is the case or ==87960== you are not sure, please let us know and we'll try to fix it. ==87960== Either way, Valgrind will now raise a SIGILL signal which will ==87960== probably kill your program. ==87960== ==87960== Process terminating with default action of signal 4 (SIGILL) ==87960== Illegal opcode at address 0x303DAB ==87960== at 0x303DAB: frexp$fenv_access_off (in /usr/lib/libSystem.B.dylib) ==87960== by 0x8471F: avmplus::D2A::D2A(double, int, int) (MathUtils.cpp:2068) ==87960== by 0x84879: avmplus::MathUtils::convertDoubleToString(avmplus::AvmCore*, double, int, int) (MathUtils.cpp:922) ==87960== by 0x50343: avmplus::AvmCore::doubleToString(double) (AvmCore.cpp:3957) ==87960== by 0x50850: avmplus::AvmCore::string(int) (AvmCore.cpp:2313) ==87960== by 0x5095B: avmplus::AvmCore::coerce_s(int) (AvmCore.cpp:2289) ==87960== by 0x1E58BC7: ??? ==87960== by 0x1E583D4: ??? ==87960== by 0x795ED: avmplus::FunctionObject::call(int, int*) (MethodEnv-inlines.h:147) ==87960== by 0x7ED69: avmplus::interpBoxed(avmplus::MethodEnv*, int, int*) (instr-inlines.h:116) ==87960== by 0x7798C: avmplus::BaseExecMgr::invoke_interp_nocoerce(avmplus::MethodEnv*, int, int*) (exec.cpp:782) ==87960== by 0x779CF: avmplus::BaseExecMgr::init_invoke_interp_nocoerce(avmplus::MethodEnv*, int, int*) (exec.cpp:193) ==87960==
Blocks: 509020
details: vex x86->IR: unhandled instruction bytes: 0x66 0xF 0xBF 0x44 ==880== valgrind: Unrecognised instruction at address 0x307dab. ... ==880== Process terminating with default action of signal 4 (SIGILL) ==880== Illegal opcode at address 0x307DAB ==880== at 0x307DAB: frexp$fenv_access_off (in /usr/lib/libSystem.B.dylib) Actual instruction: 0x97c42dab <frexp$fenv_access_off+107>: movsww 0x8(%esp),%ax
https://bugs.kde.org/show_bug.cgi?id=250799 FYI, this is x86 only
closing this was addressed with testconfig skips and there's a valgrind bug logged for it
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
bulk verifying resolved !fixed issues
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.