From: Jim Blandy <jimb@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: rda@sources.redhat.com
Subject: RFA: make more rda/unix/thread-db.c functions static
Date: Tue, 21 Sep 2004 21:56:00 -0000 [thread overview]
Message-ID: <vt2isa7p9t0.fsf@zenia.home> (raw)
How's this look?
2004-09-21 Jim Blandy <jimb@theseus.home>
* thread-db.c (thread_db_detach, thread_db_set_gen,
thread_db_thread_id): Make these functions static.
Index: rda/unix/thread-db.c
===================================================================
RCS file: /cvs/cvsfiles/devo/rda/unix/thread-db.c,v
retrieving revision 1.19
diff -c -p -r1.19 thread-db.c
*** rda/unix/thread-db.c 18 May 2004 06:12:54 -0000 1.19
--- rda/unix/thread-db.c 21 Sep 2004 21:52:33 -0000
*************** thread_db_open (struct gdbserv *serv, in
*** 873,879 ****
thread_db interface, but it's not really where this should
be done. */
! void
thread_db_detach (struct gdbserv *serv, struct gdbserv_target *target)
{
struct child_process *process = gdbserv_target_data (serv);
--- 873,879 ----
thread_db interface, but it's not really where this should
be done. */
! static void
thread_db_detach (struct gdbserv *serv, struct gdbserv_target *target)
{
struct child_process *process = gdbserv_target_data (serv);
*************** thread_db_get_gen (struct gdbserv *serv)
*** 1107,1120 ****
Handle 'Q' requests:
*/
! void
thread_db_set_gen (struct gdbserv *serv)
{
if (parentvec.process_set_gen)
parentvec.process_set_gen (serv);
}
! void
thread_db_thread_id (struct gdbserv *serv,
struct gdbserv_thread *thread,
struct gdbserv_reg *id)
--- 1107,1120 ----
Handle 'Q' requests:
*/
! static void
thread_db_set_gen (struct gdbserv *serv)
{
if (parentvec.process_set_gen)
parentvec.process_set_gen (serv);
}
! static void
thread_db_thread_id (struct gdbserv *serv,
struct gdbserv_thread *thread,
struct gdbserv_reg *id)
next reply other threads:[~2004-09-21 21:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-21 21:56 Jim Blandy [this message]
2004-09-22 4:29 ` Kevin Buettner
2004-09-22 19:00 ` Jim Blandy
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=vt2isa7p9t0.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=kevinb@redhat.com \
--cc=rda@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).