From: Andrew Cagney <ac131313@cygnus.com>
To: David Smith <dsmith@redhat.com>
Cc: GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: [RFC, RFA] multi-arch PREPARE_TO_PROCEED()
Date: Wed, 04 Apr 2001 14:54:00 -0000 [thread overview]
Message-ID: <3ACB97EC.C59C4CB3@cygnus.com> (raw)
In-Reply-To: <3AC88BF9.1060009@redhat.com>
David Smith wrote:
> hppa-tdep.c linux-thread.c lin-lwp.c m3-nat.c
> Switch "inferior_pid"? X X
> Flush cached frames? X X
> Flush register data? X X
> Update "stop_pc"?
> Select a new frame?
>
> linux-thread.c just sets an internal variable (linuxthreads_step_pid) and
> then does some magic with that variable in linuxthreads_resume(). m3-nat.c
> calls a Mach3 specific switch_to_thread() function, which doesn't change
> inferior_pid at all (?).
Yes, ok. Can of worms... Ulgh. I'd check things in as they are.
Perhaphs just add a comment to each of the existing implementations
suggesting that they are potentially redundant.
Andrew
next prev parent reply other threads:[~2001-04-04 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-29 18:25 David Smith
2001-03-30 12:16 ` Andrew Cagney
2001-04-02 7:28 ` David Smith
2001-04-04 14:54 ` Andrew Cagney [this message]
2001-04-06 10:55 ` David Smith
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=3ACB97EC.C59C4CB3@cygnus.com \
--to=ac131313@cygnus.com \
--cc=dsmith@redhat.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