Source Locations

class gccjit.Location

A gccjit.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.

You can construct them using gccjit.Context.new_location().

You need to enable gccjit.BoolOption.DEBUGINFO on the gccjit.Context for these locations to actually be usable by the debugger:

ctxt.set_bool_option(gccjit.BoolOption.DEBUGINFO, True)

gccjit.Location instances are optional; most API entrypoints accepting one default to None.

Faking it

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 gccjit.Context.dump_to_file():

ctxt.dump_to_file(b'/tmp/something.c', True)

This will dump C-like code to the given path. If the update_locations argument is True, this will also set up gccjit.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.