[patch] Add "debug jit" for easier tracing of JIT support internals

Paul Pluzhnikov ppluzhnikov@google.com
Thu Jan 6 19:52:00 GMT 2011


On Thu, Jan 6, 2011 at 11:44 AM, Tom Tromey <tromey@redhat.com> wrote:

> Could we go even further, and just specify the name of the parameter and
> then some generic documentation about it?  The set- and show-docs are
> usually pretty useless.
>
> Something like:
>
> add_setshow_zinteger_cmd ("jit", class_maintenance, &jit_debug,
>                          _("JIT debugging"),
>                          _("When non-zero, JIT debugging is enabled."),
>                          &setdebuglist, &showdebuglist);
>
> Then:
>
> (gdb) help show debug jit
> Show the "JIT debugging" setting.
> Usage: show debug jit
> When non-zero, JIT debugging is enabled.

Just to avoid any confusion, "JIT debugging" (as in "GDB will set breakpoint,
read in-memory JITed files, etc.") is (currently) always enabled.

What 'set debug jit 1' turns on is debugging of what "JIT debugging"
is doing internally :-)

-- 
Paul Pluzhnikov



More information about the Gdb-patches mailing list