It should be possible to add gdb line mapping with `#line` directives in the output, I think. With a little work, it should also be possible to support inspecting Torque variables, instead of having to inspect registers and figure out what refers to what, and calculating on-stack variables yourself.
In the past, debugging CSA code was mostly (at least for me), done using a combination of the DebugBreak() macro to produce int3 on x86, and the Print() macros for printf-style debugging. Since Torque is just a DSL for creating CSA builtins, the same approach should still work. It’s just a bit more of a headache than having better debugger integration would be. > On Jun 22, 2018, at 1:20 AM, cyril <hit.liushenr...@gmail.com> wrote: > > I just want to debug the code in ".tq" file or the code which is created by > torque > > 在 2018年6月22日星期五 UTC+8上午11:34:30，cyril写道： >> >> Recently, I discovered that v8 has added a module named torque. Anyone know >> how to debug it ?? > > -- > -- > 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 from this group and stop receiving emails from it, send an > email to v8-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- -- 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 from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
