mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: peterb@telerama.com (Peter Berger)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Pthreads, linux, gdb, oh my! (fwd)
Date: Fri, 8 Dec 2000 17:18:59 +0000 (GMT)	[thread overview]
Message-ID: <E144RAj-0004BT-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.BSI.4.02.10012081150130.17198-100000@frogger.telerama.com> from "Peter Berger" at Dec 08, 2000 11:53:07 AM

> I have seen two failure modes:  on my machine (linux 2.2.5-22, glibc
> 2.1.1), when run under gdb 5.0, the created pthreads stick around as

glibc 2.1.1 definitely has problems with several bits of pthreads. You
want 2.1.3 or higher I believe.

> zombies until the machine runs out of resources.  On some friends'
> machines (kernel 2.2.15, glibc 2.1.94), the program creates one pthread,
> waits for it to exit, and then exits.
> 
> and happy, and look forward to finding out what it is.  If it's a kernel
> bug, I submit that this makes pthreads unusable, and want to inquire if
> anyone is working on fixing this?

Its unlikely to be remotely kernel related

>   tg->running++;
>   if (tg->running >= tg->created) {

tg->created may be out of date

>       /* Create a thread that will run and exit. */
>       rc = pthread_create(thread, attr, (void *)threads_test_count_seq_proc, tg

You can create it, count it, then up tg->created out of order



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-08 17:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-08 16:53 Peter Berger
2000-12-08 17:18 ` Alan Cox [this message]
2000-12-08 19:43   ` Peter Berger
2000-12-09  0:02     ` Alan Cox
2000-12-09  6:34 ` Kevin Buhr
2000-12-09 15:15   ` Peter Berger
     [not found] <Pine.BSI.4.02.10012081708350.130-100000@frogger.telerama.c om>
2000-12-08 21:21 ` Petr Vandrovec
2000-12-08 22:15   ` Peter Berger
2000-12-08 22:31   ` David Relson

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=E144RAj-0004BT-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterb@telerama.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

all inboxes | Powered by JetHome®