aboutsummaryrefslogtreecommitdiff
path: root/gdb/i386-nbsd-nat.c
diff options
context:
space:
mode:
authorSimon Marchi <simon.marchi@polymtl.ca>2020-07-22 15:56:07 +0200
committerTankut Baris Aktemur <tankut.baris.aktemur@intel.com>2020-07-22 15:56:07 +0200
commit77208eb7e24a2bad8771f3958d9cd2e06144c654 (patch)
tree0bbf3164f475c3cd20ede6f9f15abfea98e62749 /gdb/i386-nbsd-nat.c
parent8c1c720faa4fb1ddc0c89dd60979361a8e11268a (diff)
downloadgdb-77208eb7e24a2bad8771f3958d9cd2e06144c654.zip
gdb-77208eb7e24a2bad8771f3958d9cd2e06144c654.tar.gz
gdb-77208eb7e24a2bad8771f3958d9cd2e06144c654.tar.bz2
gdb/jit: move cached_code_address and jit_breakpoint to jiter_objfile_data
This is in preparation for allowing more than one JITer objfile per program space. Once we do that, each JITer objfile will have its own JIT breakpoint (on the __jit_debug_register_code function it provides). The cached_code_address field is just the runtime / relocated address of that symbol. Since they are going to become JITer-objfile-specific and not program-space-specific, move these fields from jit_program_space_data to jiter_objfile_data. gdb/ChangeLog: 2020-07-22 Simon Marchi <simon.marchi@polymtl.ca> * jit.h (struct jiter_objfile_data) <cached_code_address, jit_breakpoint>: Move to here from ... * jit.c (jit_program_space_data): ... here. (jiter_objfile_data::~jiter_objfile_data): Update. (jit_breakpoint_deleted): Update. (jit_breakpoint_re_set_internal): Update.
Diffstat (limited to 'gdb/i386-nbsd-nat.c')
0 files changed, 0 insertions, 0 deletions