Hi Zaheer, GDB has no symbols for the generated code, so you can't use it it to debug the jit code as you would with usual code. (.ou could still use gdb to disassemble, display memory, or step through the assembly code, but I doubt that's what you want to do.)
However you should find what you need in the shell options: ./shell_g --help | grep trace I think --trace_calls is what you are looking for. Cheers, Alexandre On Thu, Dec 30, 2010 at 7:43 AM, Zaheer Ahmad <[email protected]> wrote: > hi, > I dont currently get backtraces for the JIT code (js calls) on ARM (gdb > 6.6). Is there a work around for the same? > > Thanks, > Zaheer > > -- > v8-users mailing list > [email protected] > http://groups.google.com/group/v8-users -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
