On Tuesday, April 23, 2013 1:52:13 AM UTC-7, Jakob Kummerow wrote: > > ... >> >> Is there any strategy for this kind of problem? >> >> > 1) Build and run in Debug mode. It contains a bunch of checks that help > catch at least some types of mistakes. >
Yes, I switched to Debug always after I discovered that Release mode crashes give stack traces that are often misleading. > 2) Run in GDB and inspect the situation. Maybe the type of broken objects, > or parameters present at various points in the call stack, or anything else > you may spot helps with figuring out what's going on. > > > And as Andrei said, if you want help, it would be good to share some code. > > > I'll take a wild guess here and assume that you're talking about > https://codereview.chromium.org/14362015/. If that's correct, then at a > quick glance the change in > https://codereview.chromium.org/14362015/diff/1/Source/bindings/v8/custom/V8InjectedScriptHostCustom.cpp > looks > suspicious: You're returning handles created in a HandleScope that's going > out of scope when returning, rendering the handles created in it invalid. > I'll update the patch; since I posted it I learned about the requirement to call "Close()" to return handles. > (Running in Debug mode should quickly ascertain whether this is the cause > of the problem.) > Hmm, what should I be looking for ? I'm running in debug, but not quickly ascertaining ;-) jjb -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
