It doesn't. trace_calls seems related to dumping all the js traces. what iam looking for is to get full backtraces on arm similar to x86. Its possible that gdb doesnt understand the js frame layout on arm and hence it fails.
appreciate any pointers. Thanks, Zaheer On Thu, Dec 30, 2010 at 4:47 PM, Alexandre Rames <[email protected]>wrote: > So did the --trace_calls option solve your problem? > > Alexandre > > > > On Thu, Dec 30, 2010 at 11:03 AM, Zaheer Ahmad <[email protected]>wrote: > >> On Thu, Dec 30, 2010 at 3:29 PM, Alexandre Rames < >> [email protected]> wrote: >> >>> 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.) >>> >> Yeah, i meant the gdb does not show the complete trace on ARM, it stops >> after the first JIT frame. >> > >>> 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 >> >> >> -- >> 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 > -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
