Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Hise <kevinh@ridgecrest.ca.us>
To: GDB Patches <gdb-patches@sourceware.cygnus.com>
Subject: Linux thread debugging patch?
Date: Fri, 09 Mar 2001 23:13:00 -0000	[thread overview]
Message-ID: <4.1.20010309231024.00961f00@mail.ridgecrest.ca.us> (raw)

Is there a patch for 5.0 that corrects the problems debugging PThreads on
Linux?  I have tried a patch that affected 'lin-thread.c' but it had no
effect (I just make'd GDB and ran it without doing a 'make install').
Should I just wait for GDB 5.1 or 5.2?

Thanks for any help.
/*
Kevin Hise

email: kevinh@ridgecrest.ca.us
voice: 760/384-3855
WWW: http://www.ridgenet.net/~kevinh/

"There's trouble in the Kingdom
  send a message to the King!" - Kings-X

#198118 with the Linux Counter, http://counter.li.org

America kills 169 babies every hour of every day, over 38 million since 1973.
http://www.roevwade.org/   http://www.abortionfacts.com/
http://www.abortioncancer.com/   http://www.nrlc.org/RU486/Index.html
*/


             reply	other threads:[~2001-03-09 23:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-09 23:13 Kevin Hise [this message]
2001-03-12 11:48 ` Michael Snyder
2001-03-13  2:57   ` Mark Kettenis

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=4.1.20010309231024.00961f00@mail.ridgecrest.ca.us \
    --to=kevinh@ridgecrest.ca.us \
    --cc=gdb-patches@sourceware.cygnus.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