From: "Martin M. Hunt" <hunt@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] regcache fix
Date: Wed, 20 Mar 2002 18:16:00 -0000 [thread overview]
Message-ID: <200203210215.g2L2FYY17286@localhost.localdomain> (raw)
In-Reply-To: <3C98F40E.1000500@cygnus.com>
Committed.
On Wednesday 20 March 2002 12:41 pm, Andrew Cagney wrote:
> > Currently build_regcache is called 3 times, once at initialization,
> > before any architectures are registered, once when the host is
> > registered and once when the target is registered. I don't see
> > any reason for the first call, and in some non-multiarched
> > targets it can cause core dumps.
>
> (the second time is for bfd's default architecture)
>
> Yep, ok! There is no longer a need to do this, and other similar,
> calls. Will make understanding things a little bit easier.
>
> Thanks for testing this on non-multi-arch as well.
prev parent reply other threads:[~2002-03-21 2:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-19 18:29 Martin M. Hunt
2002-03-20 12:41 ` Andrew Cagney
2002-03-20 18:16 ` Martin M. Hunt [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=200203210215.g2L2FYY17286@localhost.localdomain \
--to=hunt@redhat.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