This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [rfc] [17/17] Get rid of current_gdbarch in go32-nat.c
> Date: Wed, 24 Oct 2007 07:47:45 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: deuling@de.ibm.com, gdb-patches@sourceware.org, uweigand@de.ibm.com
>
> A gdbarch includes lots of information. Some examples:
>
> - What registers are available, including pseudo-registers and
> emulated registers. E.g., if DJGPP supports running binaries
> with and without MMX support available more than one gdbarch might
> be needed.
>
> - The sizes of basic types. E.g., if some versions of DJGPP used
> a 64-bit long double and other versions used an 80-bit long double.
> This transition seems to happen on many platforms at least once.
>
> - Mapping of debug info numbers to register numbers. E.g., if two
> compilers used different numbers this might be handled by setting
> a different function pointer in the gdbarch depending on the loaded
> binary.
Thanks, I'm convinced.
Btw, the above sounds like something that would be good to have in
gdbint.texinfo, if you get my drift ;-)