From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: PATCH: Fork event updates, part the ninth
Date: Sun, 15 Dec 2002 12:07:00 -0000 [thread overview]
Message-ID: <20021215190317.GA25451@nevyn.them.org> (raw)
Pulling leftovers from my working directory... this patch kills what used to
be ->to_next, which hasn't been used for some time. Committed.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
2002-12-15 Daniel Jacobowitz <drow@mvista.com>
* target.c (update_current_target): Don't inherit DONT_USE.
* target.h (struct target_ops): Remove DONT_USE.
(target_next): Remove macro.
Index: gdb/target.c
===================================================================
RCS file: /cvs/src/src/gdb/target.c,v
retrieving revision 1.47
diff -u -p -r1.47 target.c
--- gdb/target.c 12 Dec 2002 01:39:34 -0000 1.47
+++ gdb/target.c 15 Dec 2002 18:56:17 -0000
@@ -609,7 +609,6 @@ update_current_target (void)
INHERIT (to_get_current_exception_event, t);
INHERIT (to_pid_to_exec_file, t);
INHERIT (to_stratum, t);
- INHERIT (DONT_USE, t);
INHERIT (to_has_all_memory, t);
INHERIT (to_has_memory, t);
INHERIT (to_has_stack, t);
Index: gdb/target.h
===================================================================
RCS file: /cvs/src/src/gdb/target.h,v
retrieving revision 1.33
diff -u -p -r1.33 target.h
--- gdb/target.h 12 Dec 2002 01:39:34 -0000 1.33
+++ gdb/target.h 15 Dec 2002 18:56:18 -0000
@@ -295,8 +295,6 @@ struct target_ops
struct exception_event_record *(*to_get_current_exception_event) (void);
char *(*to_pid_to_exec_file) (int pid);
enum strata to_stratum;
- struct target_ops
- *DONT_USE; /* formerly to_next */
int to_has_all_memory;
int to_has_memory;
int to_has_stack;
@@ -779,11 +777,6 @@ extern void target_load (char *arg, int
#define target_get_current_exception_event() \
(*current_target.to_get_current_exception_event) ()
-
-/* Pointer to next target in the chain, e.g. a core file and an exec file. */
-
-#define target_next \
- (current_target.to_next)
/* Does the target include all of memory, or only part of it? This
determines whether we look up the target chain for other parts of
next reply other threads:[~2002-12-15 19:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-15 12:07 Daniel Jacobowitz [this message]
2002-12-16 8:35 ` 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=20021215190317.GA25451@nevyn.them.org \
--to=drow@mvista.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