From: Andrew Cagney <ac131313@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: target_op(..) -> target_op(target, ...) obvious
Date: Thu, 09 Oct 2003 13:55:00 -0000 [thread overview]
Message-ID: <3F8568C2.9040306@redhat.com> (raw)
In-Reply-To: <3F855EFF.9080300@redhat.com>
> As part of the on-going OO of GDB, the "target vector" is one of the next things up for treatment. I'd like to be sure that everyones ok with the mechanical transformatioin:
>
> target_OP (...) -> taget_OP (target, ...)
>
> being considered "fairly obvious" (post patch, give it a few days, commit patch). Pushing the target around is going to involve touching files across maintenance boundraries.
[Not my day.]
The rationale is the same as for the architecture vector along with the
push to eliminate global thread/frame state. It is to make it possible
to have multiple instances of a specific target. For instance,two
ptrace inferior's, or two active remotes.
Andrew
next prev parent reply other threads:[~2003-10-09 13:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 13:13 Andrew Cagney
2003-10-09 13:55 ` Andrew Cagney [this message]
2003-10-09 19:39 ` Jim Blandy
2003-10-09 20:36 ` Andrew Cagney
2003-10-10 2:06 ` remote serial protocol - gdbserver saleru.raja
2003-10-10 2:28 ` Andrew Cagney
2003-10-10 5:15 ` Raja Saleru
2003-10-11 15:40 ` Andrew Cagney
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=3F8568C2.9040306@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@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