A gcc_jit_location encapsulates a source code location, so that you can (optionally) associate locations in your language with statements in the JIT-compiled code, allowing the debugger to single-step through your language.
gcc_jit_location instances are optional: you can always pass NULL to any API entrypoint accepting one.
You can construct them using
You need to enable
gcc_jit_contextfor these locations to actually be usable by the debugger:
gcc_jit_context_set_bool_option ( ctxt, GCC_JIT_BOOL_OPTION_DEBUGINFO, 1);
gcc_jit_location *gcc_jit_context_new_location(gcc_jit_context *ctxt, const char *filename, int line, int column)¶
Create a gcc_jit_location instance representing the given source location.
filenamemust be non-NULL. The call takes a copy of the underlying string, so it is valid to pass in a pointer to an on-stack buffer.
If you don’t have source code for your internal representation, but need
to debug, you can generate a C-like representation of the functions in
your context using
gcc_jit_context_dump_to_file (ctxt, "/tmp/something.c", 1 /* update_locations */);
This will dump C-like code to the given path. If the update_locations argument is true, this will also set up gcc_jit_location information throughout the context, pointing at the dump file as if it were a source file, giving you something you can step through in the debugger.