From: Eli Zaretskii <eliz@delorie.com>
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 [thread overview]
Message-ID: <200107281617.MAA21008@delorie.com> (raw)
In-Reply-To: <3B62D14B.2030201@cygnus.com>
> Date: Sat, 28 Jul 2001 10:50:51 -0400
> From: Andrew Cagney <ac131313@cygnus.com>
>
> > 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.
prev parent reply other threads:[~2001-07-28 9:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-25 20:38 Andrew Cagney
2001-07-25 23:51 ` Eli Zaretskii
2001-07-26 11:43 ` Andrew Cagney
2001-07-27 2:36 ` Eli Zaretskii
2001-07-27 13:36 ` Andrew Cagney
[not found] ` <1438-Sat28Jul2001103025+0300-eliz@is.elta.co.il>
2001-07-28 7:50 ` Andrew Cagney
2001-07-28 9:17 ` Eli Zaretskii [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200107281617.MAA21008@delorie.com \
--to=eliz@delorie.com \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox