This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Some regset-related cleanup for i386bsd-nat.c


Mark Kettenis <kettenis@chello.nl> writes:


	* i386bsd-nat.c: Don't include "gregset.h".
	(supply_gregset, fill_gregset): Make static.
	(supply_fpregset, fill_fpregset): Remove.


I just noticed this in one of my builds. I'm attempting to modernize
and prepare my NetBSD thread support code for integration, and that
code uses the {supply,fill}_{regset,fpregset} functions to implement
the thread-specific fetch_registers and store_registers, based on
register context passed back from the pthread debugging library (It
was quite a boon when I ported it forward from 5.0 to 5.3 and got
these functions to use). If these are removed, is there a good way for
an architecture-neutral bit of code like nbsd-thread.c to go back and
forth between GDB's register storage and native register storage?

Have a look at regsets.[hc], the method:
set_gdbarch_regset_from_core_section (gdbarch, ppc_linux_regset_from_core_section);
they set the general direction for where GDB is going.


Andrew



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]