Closed Bug 424555 Opened 17 years ago Closed 17 years ago

Valgrind - Invalid write running debug js shell with no arguments (64bit)

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: bc, Unassigned)

Details

(Keywords: valgrind)

CentOS 5 64 valgrind --tool=memcheck ./js vex amd64->IR: unhandled instruction bytes: 0x6 0xA1 0xEF 0xFF ==24450== Warning: client switching stacks? SP change: 0x7FEFFF230 --> 0xFEFFF208 ==24450== to suppress, use: --max-stackframe=40 or greater ==24450== Invalid write of size 4 ==24450== at 0x509CE3: readline (in /work/mozilla/builds/1.9.0/mozilla/js/src/Linux_All_DBG.OBJ/js) ==24450== Address 0xC4FC65 is not stack'd, malloc'd or (recently) free'd ==24450== ==24450== Process terminating with default action of signal 11 (SIGSEGV) ==24450== Access not within mapped region at address 0xC4FC65 ==24450== at 0x509CE3: readline (in /work/mozilla/builds/1.9.0/mozilla/js/src/Linux_All_DBG.OBJ/js) ==24450== ==24450== Invalid write of size 8 ==24450== at 0x48022D8: _vgnU_freeres (vg_preloaded.c:56) ==24450== Address 0xFEFFF200 is on thread 1's stack = doesn't happen if you add -f foo.js for a simple print script.
Flags: in-litmus-
appears to be 64 bit only.
Summary: Valgrind - Invalid write running debug js shell with no arguments → Valgrind - Invalid write running debug js shell with no arguments (64bit)
invalid. I had copied a tree from one machine to to another and didn't realize that make Makefile.ref clean in js/src *didn't* clean editline. So there were old 32bit editline binaries getting linked.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.