From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Jacobowitz To: Kevin Buettner Cc: Andrew Cagney , gdb@sources.redhat.com Subject: Re: [RFC] Changes to *_*regset functions Date: Fri, 13 Jul 2001 12:43:00 -0000 Message-id: <20010713124314.A4541@nevyn.them.org> References: <20010713102605.A32410@nevyn.them.org> <3B4F4223.8030405@cygnus.com> <1010713193513.ZM20388@ocotillo.lan> X-SW-Source: 2001-07/msg00138.html On Fri, Jul 13, 2001 at 12:35:13PM -0700, Kevin Buettner wrote: > On Jul 13, 2:46pm, Andrew Cagney wrote: > > > > Along with the cross-core handling, and eventually cross-thread support, I > > > want to multi-arch supply_gregset/fill_gregset/supply_fpregset/fill_fpregset, > > > and make them target rather than native functions where possible. The issue, > > > of course, is that the *regset_t and *reg_t types are not available to us > > > when cross compiling, and attempting to make them available seems the wrong > > > way to go. > > > > > > Do they belong in gdbarch? gdbarch contains things that describe the > > target systems ISA, ABI, ... > > > > Something like supply_gregset() might use gdbarch. I don't know that it > > belongs in multi-arch. > > For Daniel's purposes, supply_gregset() does need to be multi-arch. > Imagine wanting to debug UnixWare, Solaris/x86, Linux, and FreeBSD > core files from a NetBSD/PPC platform. In other words, think of the > core file format as an extension of the ABI. Exactly what I wanted to address. The other issue is with thread libraries; thread_db makes calls down to supply_gregset and fill_gregset, so if we ever share that layer between two ABIs, this will need to happen. -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer