Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: gdb-patches@sources.redhat.com
Subject: Re: [rfa/threads] Eliminate lin-lwp.c
Date: Mon, 27 Sep 2004 19:58:00 -0000	[thread overview]
Message-ID: <415870C3.3000108@gnu.org> (raw)
In-Reply-To: <4149B268.3060506@gnu.org>

> Hello,
> 
> Ref: http://sources.redhat.com/ml/gdb/2004-09/msg00136.html
> This patch performs a simple minded merge of lin-lwp.c into linux-nat.c.
> 
> With this change in place the task of switching to the inheritance target vector, and having a GNU/Linux specific target vector, become possible.
> 
> Tested on i386 FC3ish GNU/Linux with no regressions (as expected, this is a mechanical change).
> 
> ok?

M;kayed & committed.

> Index: ChangeLog
> 2004-09-16  Andrew Cagney  <cagney@gnu.org>
> 
> 	* lin-lwp.c: Delete file.
> 	* linux-nat.c: Include "gdb_assert.h", "gdb_string.h", <unistd.h>,
> 	<sys/syscall.h>, "gdbthread.h", "gdbcmd.h", "regcache.h".
> 	(status_to_str, init_lwp_list, add_lwp, delete_lwp)
> 	(find_lwp_pid, iterate_over_lwps, lin_lwp_attach_lwp)
> 	(linux_nat_attach, detach_callback, linux_nat_detach)
> 	(resume_callback, resume_clear_callback, linux_nat_resume)
> 	(kill_lwp, linux_nat_handle_extended, wait_lwp, stop_callback)
> 	(stop_wait_callback, linux_nat_has_pending, flush_callback)
> 	(status_callback, running_callback, count_events_callback)
> 	(select_singlestep_lwp_callback, select_event_lwp_callback)
> 	(cancel_breakpoints_callback, select_event_lwp, resumed_callback)
> 	(child_wait, stop_and_resume_callback, linux_nat_wait)
> 	(kill_callback, kill_wait_callback, linux_nat_kill)
> 	(linux_nat_create_inferior, linux_nat_mourn_inferior)
> 	(linux_nat_xfer_memory, linux_nat_thread_alive)
> 	(linux_nat_pid_to_str, init_linux_nat_ops, sigchld_handler)
> 	(_initialize_linux_nat): New functions.
> 	* Makefile.in: Update all dependencies.
> 	* config/sparc/linux64.mh (NATDEPFILES): Remove lin-lwp.o.
> 	* config/sparc/linux.mh (NATDEPFILES): Remove lin-lwp.o.
> 	* config/s390/s390.mh (NATDEPFILES): Remove lin-lwp.o.
> 	* config/powerpc/ppc64-linux.mh (NATDEPFILES): Remove lin-lwp.o.
> 	* config/powerpc/linux.mh (NATDEPFILES): Remove lin-lwp.o.
> 	* config/pa/linux.mh (NATDEPFILES): Remove lin-lwp.o.
> 	* config/mips/linux.mh (NATDEPFILES): Remove lin-lwp.o.
> 	* config/m68k/linux.mh (NATDEPFILES): Remove lin-lwp.o.
> 	* config/ia64/linux.mh (NATDEPFILES): Remove lin-lwp.o.
> 	* config/i386/linux64.mh (NATDEPFILES): Remove lin-lwp.o.
> 	* config/i386/linux.mh (NATDEPFILES): Remove lin-lwp.o.
> 	* config/arm/linux.mh (NATDEPFILES): Remove lin-lwp.o.
> 	* config/alpha/alpha-linux.mh (NATDEPFILES): Remove lin-lwp.o.
> 


      parent reply	other threads:[~2004-09-27 19:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-16 15:36 Andrew Cagney
2004-09-16 15:48 ` Daniel Jacobowitz
2004-09-16 16:05   ` Andrew Cagney
2004-09-16 16:22     ` Daniel Jacobowitz
2004-09-16 16:32       ` Andrew Cagney
2004-09-16 17:38         ` Daniel Jacobowitz
2004-09-16 20:12           ` Andrew Cagney
2004-09-16 20:29             ` Daniel Jacobowitz
2004-09-16 21:13               ` Andrew Cagney
2004-09-16 21:25                 ` Daniel Jacobowitz
2004-09-16 22:23                   ` Andrew Cagney
2004-09-17 22:07                   ` Michael Snyder
2004-09-27 19:58 ` Andrew Cagney [this message]

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=415870C3.3000108@gnu.org \
    --to=cagney@gnu.org \
    --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