From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eli Zaretskii To: ac131313@cygnus.com Cc: gdb-patches@sources.redhat.com Subject: Re: [rfa] libgdb updates to doco Date: Sat, 28 Jul 2001 09:17:00 -0000 Message-id: <200107281617.MAA21008@delorie.com> References: <3B606479.2070205@cygnus.com> <5567-Fri27Jul2001123713+0300-eliz@is.elta.co.il> <3B61D09E.1000902@cygnus.com> <1438-Sat28Jul2001103025+0300-eliz@is.elta.co.il> <3B62D14B.2030201@cygnus.com> X-SW-Source: 2001-07/msg00687.html > Date: Sat, 28 Jul 2001 10:50:51 -0400 > From: Andrew Cagney > > > That's just a cookbook. It's important to have that, but it is no > > less important to understand how multi-arch works internally, to be > > able to do something beyond blindly following the cookbook. > > Hmm, not sure if you want the doco to explain how it currently works - > the swap stuff is a really nasty paramatic hack. How it _should_ work > might be useful. I'm not talking about swapping the arch, but about a list of the methods covered by the arch, and how things like registers, addresses, and chunks of memory get from the debuggee via gdbarch to GDB. This path includes many translation layers which, at least for me, are the biggest stumbling block when I'm trying to understand how things work in a certain port, and where to look for possible reasons of some snafu. > I think its like libgdb - in theory it works like ..., when working > on the reality, try to keep the theory in mind and try to make the > code more like the theory :-) I agree; but in this case even the theory is not documented.