Have you tried running the code in debug mode? V8 has a lot of assertions which might fail and point you in the direction of the error. Regards, Søren
On Mon, Mar 16, 2009 at 7:03 PM, Stephan Beal <[email protected]> wrote: > > On Mon, Mar 16, 2009 at 6:56 PM, <[email protected]> wrote: > > 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? > > It's theoretically possible, sure. v8 is quite fussy about certain > things. For example, calling Object::Cast(*myHandle) will crash if > myHandle is-not-a Object. In my experience, most of the > harder-to-avoid crashes happen right after main() exits, when certain > objects are trying to destruct after v8 has already gone through the > static destruction phase. > > As a test, try something like: > > myArray->Set( Integer::Cast(*myHandle) ) > > where myHandle is-not-an Integer. It "should" (in my experience) crash > there. Are you using: > > myArray->Set( Integer::New(...), ...) > > or the former form? (The latter should, in theory, not be a problem > unless you just happen to use whatever number v8 reserves for > NaN(???).) > > -- > ----- stephan beal > http://wanderinghorse.net/home/stephan/ > > > > --~--~---------~--~----~------------~-------~--~----~ v8-users mailing list [email protected] http://groups.google.com/group/v8-users -~----------~----~----~----~------~----~------~--~---
