From: Kevin Buettner <kevinb@cygnus.com>
To: peter@a59252.upc-a.chello.nl, gdb@sourceware.cygnus.com
Subject: Re: configuring gdb 5.x for use with threads
Date: Wed, 07 Nov 2001 02:30:00 -0000 [thread overview]
Message-ID: <1011117165348.ZM6496@ocotillo.lan> (raw)
In-Reply-To: peter@a59252.upc-a.chello.nl "Re: configuring gdb 5.x for use with threads" (Nov 17, 2:27pm)
On Nov 17, 2:27pm, peter@a59252.upc-a.chello.nl wrote:
> I rebuild my glibc+linuxthreads 2.2.4 agains my linuxkernel
> 2.4.15-pre5 SMP, a libthread_db-1.0.so was build.
Make sure that you have the following patch (to glibc) applied. I too
was having problems with debugging multithreaded programs that were
linked against libraries from glibc 2.2.4. This patch fixed the
problems that I was seeing...
2001-10-05 Kevin Buettner <kevinb@cygnus.com>
* pthread.c (__linuxthread_pthread_sizeof_descr): Change name
to __linuxthreads_pthread_sizeof_descr to match name used by
symbol_list_arr[LINUXTHREADS_PTHREAD_SIZEOF_DESCR] in
linuxthreads_db/td_symbol_list.c.
===================================================================
RCS file: /cvs/glibc/libc/linuxthreads/pthread.c,v
retrieving revision 1.86
retrieving revision 1.87
diff -u -r1.86 -r1.87
--- libc/linuxthreads/pthread.c 2001/09/12 03:51:41 1.86
+++ libc/linuxthreads/pthread.c 2001/10/07 20:19:16 1.87
@@ -211,7 +211,7 @@
h_descr);
const int __pthread_offsetof_pid = offsetof(struct _pthread_descr_struct,
p_pid);
-const int __linuxthread_pthread_sizeof_descr
+const int __linuxthreads_pthread_sizeof_descr
= sizeof(struct _pthread_descr_struct);
/* Forward declarations */
next prev parent reply other threads:[~2001-11-17 16:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20011102102321.D6507@a59252.upc-a.chello.nl>
2001-11-06 21:13 ` peter
2001-11-07 2:30 ` Kevin Buettner [this message]
2001-11-08 7:09 ` peter
2001-11-08 7:53 ` Daniel Jacobowitz
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=1011117165348.ZM6496@ocotillo.lan \
--to=kevinb@cygnus.com \
--cc=gdb@sourceware.cygnus.com \
--cc=peter@a59252.upc-a.chello.nl \
/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