From: Nick Duffek <nsd@redhat.com>
To: cagney@cygnus.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] add remote.c gdbarch thread-handling hooks
Date: Mon, 16 Jul 2001 17:40:00 -0000 [thread overview]
Message-ID: <200107170040.f6H0e1v21680@rtl.cygnus.com> (raw)
In-Reply-To: <3B537C79.9060108@cygnus.com>
On 16-Jul-2001, Andrew Cagney wrote:
>Nick, could you please post a patch of what you actually committed.
Are you saying that you weren't approving the obvious part of the patch
when you wrote the following?
>I'd assume this bit is pretty obvious and can go in as a separate
>independant patch.
Here it is again.
Nick
Index: gdb/remote.c
===================================================================
diff -up gdb/remote.c gdb/remote.c
--- gdb/remote.c Mon Jul 16 19:31:11 2001
+++ gdb/remote.c Mon Jul 16 19:30:22 2001
@@ -5235,8 +5235,8 @@ Specify the serial device it is connecte
remote_ops.to_mourn_inferior = remote_mourn;
remote_ops.to_thread_alive = remote_thread_alive;
remote_ops.to_find_new_threads = remote_threads_info;
- remote_ops.to_extra_thread_info = remote_threads_extra_info;
remote_ops.to_pid_to_str = remote_pid_to_str;
+ remote_ops.to_extra_thread_info = remote_threads_extra_info;
remote_ops.to_stop = remote_stop;
remote_ops.to_query = remote_query;
remote_ops.to_rcmd = remote_rcmd;
@@ -5644,7 +5644,8 @@ Specify the serial device it is connecte
remote_cisco_ops.to_mourn_inferior = remote_cisco_mourn;
remote_cisco_ops.to_thread_alive = remote_thread_alive;
remote_cisco_ops.to_find_new_threads = remote_threads_info;
- remote_ops.to_extra_thread_info = remote_threads_extra_info;
+ remote_cisco_ops.to_pid_to_str = remote_pid_to_str;
+ remote_cisco_ops.to_extra_thread_info = remote_threads_extra_info;
remote_cisco_ops.to_stratum = process_stratum;
remote_cisco_ops.to_has_all_memory = 1;
remote_cisco_ops.to_has_memory = 1;
@@ -5734,7 +5735,8 @@ Specify the serial device it is connecte
remote_async_ops.to_mourn_inferior = remote_async_mourn;
remote_async_ops.to_thread_alive = remote_thread_alive;
remote_async_ops.to_find_new_threads = remote_threads_info;
- remote_ops.to_extra_thread_info = remote_threads_extra_info;
+ remote_async_ops.to_pid_to_str = remote_pid_to_str;
+ remote_async_ops.to_extra_thread_info = remote_threads_extra_info;
remote_async_ops.to_stop = remote_stop;
remote_async_ops.to_query = remote_query;
remote_async_ops.to_rcmd = remote_rcmd;
next parent reply other threads:[~2001-07-16 17:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3B537C79.9060108@cygnus.com>
2001-07-16 17:40 ` Nick Duffek [this message]
2001-07-16 20:22 ` Andrew Cagney
[not found] <3B5386C6.9020904@cygnus.com>
2001-07-16 18:20 ` Nick Duffek
2001-07-16 10:26 Nick Duffek
2001-07-16 11:14 ` Andrew Cagney
2001-07-16 16:34 ` Nick Duffek
2001-07-16 12:21 ` J.T. Conklin
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=200107170040.f6H0e1v21680@rtl.cygnus.com \
--to=nsd@redhat.com \
--cc=cagney@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