On Thu, Jan 9, 2014 at 4:50 AM, ChaosPP junho0924@lge.com wrote:
I'm sorry about no make sense sentence.
I using GDB for debugging v8 ($gdb d8, using sample javascript - var
temp=10;), and trace function flow after Script::Run().
After some next, I reached CALL_GENERATED_CODE() in
OK. I Understand, Thanks.
But, may I know why the program jumps to ~SealHandleScope()?
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
---
You received this message because you are subscribed to the Google Groups
v8-users group.
To unsubscribe
On Thu, Jan 9, 2014 at 10:04 AM, ChaosPP junho0924@lge.com wrote:
OK. I Understand, Thanks.
But, may I know why the program jumps to ~SealHandleScope()?
Because right after the CALL_GENERATED_CODE there's a block end where a
SealHandleScope object goes out of scope, hence its destructor
Hmm... Util classes(handle, handlescope, isolate ...) maybe need to more
study. Thanks :)
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
---
You received this message because you are subscribed to the Google Groups
v8-users group.
To
I'm sorry about no make sense sentence.
I using GDB for debugging v8 ($gdb d8, using sample javascript - var
temp=10;), and trace function flow after Script::Run().
After some next, I reached CALL_GENERATED_CODE() in execution.cc::Invoke().
When step( (gdb) s ) at the function,
the program