The only time I call SetAccessor is to create function templates and bind C++ calls to them. Do you think this could happen during runtime when creating an array in C++ and sending into script?
On Mar 16, 10:07 am, Stephan Beal <[email protected]> wrote: > If i interpret that correctly (but i'm largely guessing here), it's > trying to use NaN (Not-a-Number) as an array index. Perhaps your > property setting code is using end-user data without making sure that > it's numeric? > > :-? > > On 3/16/09, [email protected] <[email protected]> wrote: > > > > > > > Hello, > > > I have written a layer on top of V8 and am running on a custom Fedora > > Core 2 kernel. Every thing runs great except every once in a while I > > get a segmentation fault when trying to call SetAccessor. I believe > > the seg fault stemmed from that call, but I cant be sure as the > > coredump file is minimal. > > > (gdb) where > > #0 0x0829a238 in v8::FunctionTemplate::AddInstancePropertyAccessor () > > #1 0x084c437c in v8::internal::Heap::nan_value_ () > > #2 0x084c437c in v8::internal::Heap::nan_value_ () > > #3 0x0a13e2d8 in ?? () > > #4 0x0a13e2d0 in ?? () > > #5 0x00000000 in ?? () > > > Was posting to see if anyone had any ideas on how this would come > > about in the engine. > > -- > ----- stephan bealhttp://wanderinghorse.net/home/stephan/ --~--~---------~--~----~------------~-------~--~----~ v8-users mailing list [email protected] http://groups.google.com/group/v8-users -~----------~----~----~----~------~----~------~--~---
