Also, my apologies if I should be submitting this to the user list or I'm not going through the right channels.
Please let me know anything I can do to give more useful feed back. I'm running Node.js 0.2.5 which uses v8-2.3.8, forgot to mention that before On Dec 15, 9:56 am, CoolAJ86 <[email protected]> wrote: > I'm using node.js on ARM and it segfaults after just a few minutes of > running. > > Are any of these options not safe? Am I omitting something? > > export CC_OPTS="-ggdb3" > export TARGET_ARCH="-march=armv7-a" # must be at least armv5te > export TARGET_TUNE="-mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp - > mthumb-interwork -mno-thumb" # optional > > export CCLD="gcc ${CC_OPTS} ${TARGET_ARCH} ${TARGET_TUNE}" > export CC="gcc ${CC_OPTS} ${TARGET_ARCH} ${TARGET_TUNE}" > export CXX="g++ ${CC_OPTS} ${TARGET_ARCH} ${TARGET_TUNE}" > > ./configure > make > make install > > Here's the stacktrace > > Program received signal SIGSEGV, Segmentation fault. > 0x001794d8 in > v8::internal::StringDictionary::FindEntry(v8::internal::String*) () > Current language: auto > The current source language is "auto; currently asm". > (gdb) bt > #0 0x001794d8 in > v8::internal::StringDictionary::FindEntry(v8::internal::String*) () > #1 0x0017a52c in > v8::internal::JSObject::LocalLookupRealNamedProperty(v8::internal::String*, > v8::internal::LookupResult*) () > #2 0x0014a68c in > v8::internal::StoreIC::Store(v8::internal::InlineCacheState, > v8::internal::Handle<v8::internal::Object>, > v8::internal::Handle<v8::internal::String>, > v8::internal::Handle<v8::internal::Object>) () > #3 0x0014a9a0 in v8::internal::StoreIC_Miss(v8::internal::Arguments) > () > #4 0x42526254 in ?? () > #5 0x42526254 in ?? () > Backtrace stopped: previous frame identical to this frame (corrupt > stack?) -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
