On Jul 4, 2012, at 05:22, Ben Noordhuis wrote: >>> Also, if you have the time and the inclination, it'd be interesting to >>> track down the cause of the bus error. >> >> I'm not sure I know how to do this, but as a start, here's what the OS X >> crash reporter has to say about it: >> >> >> Thread 0 Crashed: >> 0 mksnapshot 0x000c1e19 >> v8::internal::AllocateFixedArrayWithFiller(v8::internal::Heap*, int, >> v8::internal::PretenureFlag, v8::internal::Object*) + 441 >> 1 mksnapshot 0x000c460d >> v8::internal::Heap::AllocateHashTable(int, v8::internal::PretenureFlag) + 29 >> 2 mksnapshot 0x0017f973 >> v8::internal::HashTable<v8::internal::SymbolTableShape, >> v8::internal::HashTableKey*>::Allocate(int, v8::internal::PretenureFlag) + >> 115 >> 3 mksnapshot 0x000c8dfb >> v8::internal::Heap::CreateInitialObjects() + 203 >> 4 mksnapshot 0x000c9898 >> v8::internal::Heap::SetUp(bool) + 1160 >> 5 mksnapshot 0x0014f8ae >> v8::internal::Isolate::Init(v8::internal::Deserializer*) + 1294 >> 6 mksnapshot 0x00283579 >> v8::internal::V8::Initialize(v8::internal::Deserializer*) + 201 >> 7 mksnapshot 0x000278cf >> v8::Context::New(v8::ExtensionConfiguration*, >> v8::Handle<v8::ObjectTemplate>, v8::Handle<v8::Value>) + 1087 >> 8 mksnapshot 0x00002006 main + 166 >> (mksnapshot.cc:306) >> 9 mksnapshot 0x00001f26 start + 54 > > Can you try it with the HEAD of the v0.8 branch? I landed a couple of > patches that try to detect (and work around) buggy compilers.
The node 0.8.2 build still crashes in the same way. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
