From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: [patch] Delete lin-thread.c; Was: [patch] Delete linux-thread.c
Date: Sat, 23 Feb 2002 20:30:00 -0000 [thread overview]
Message-ID: <3C786C63.3000108@cygnus.com> (raw)
In-Reply-To: <20020223231135.A27911@nevyn.them.org>
[-- Attachment #1: Type: text/plain, Size: 331 bytes --]
> Can do. I'm wondering how it became an outling - I thought lin-thread.c
>> replaced linux-thread.c.
>
>
> It did - but very briefly, I think. Lin-lwp is the current module.
> lin-thread.c appeared in Dec. 1999, and lin-lwp in Sep. 2000; we've
> been transitioning to the latter and completed it a few months ago.
Gone!
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 878 bytes --]
2002-02-23 Andrew Cagney <ac131313@redhat.com>
* lin-thread.c: Delete file.
* configure.in (gdb_cv_struct_reg_r_gs): Update comment to refer
to gdb_proc_service.h.
* configure: Re-generate.
Index: configure.in
===================================================================
RCS file: /cvs/src/src/gdb/configure.in,v
retrieving revision 1.81
diff -u -r1.81 configure.in
--- configure.in 2002/02/23 21:54:25 1.81
+++ configure.in 2002/02/24 04:28:22
@@ -307,7 +307,7 @@
dnl For Linux/i386, glibc 2.1.3 was released with a bogus
dnl prfpregset_t type (it's a typedef for the pointer to a struct
dnl instead of the struct itself). We detect this here, and work
- dnl around it in lin-thread.c.
+ dnl around it in gdb_proc_service.h.
if test $bfd_cv_have_sys_procfs_type_prfpregset_t = yes; then
AC_MSG_CHECKING(whether prfpregset_t type is broken)
next prev parent reply other threads:[~2002-02-24 4:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-23 19:35 Andrew Cagney
2002-02-23 19:40 ` Daniel Jacobowitz
2002-02-23 20:05 ` Andrew Cagney
2002-02-23 20:11 ` Daniel Jacobowitz
2002-02-23 20:30 ` Andrew Cagney [this message]
2002-02-23 22:21 ` Michael Snyder
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=3C786C63.3000108@cygnus.com \
--to=ac131313@cygnus.com \
--cc=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