From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Peter Berger <peterb@telerama.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Pthreads, linux, gdb, oh my! (fwd)
Date: Fri, 8 Dec 2000 21:21:09 MET-1 [thread overview]
Message-ID: <F1BEC884C26@vcnet.vc.cvut.cz> (raw)
On 8 Dec 00 at 14:43, Peter Berger wrote:
> > tg->created may be out of date
> ...
> > You can create it, count it, then up tg->created out of order
>
> Well, you're right, but this is picking lint. Making this change (see
> http://peterb.telerama.com/thread-test.c for the corrected version)
> certainly doesn't make the problem go away (nor would I expect it to).
Can you tell me again (private, probably), which problem do you have?
After I fixed source to get it to compile with -W -Wall -Werror
(missing includes, wrong parameters to main...), and compiling with
-D_REENTRANT, I received nice ./a.out, which runs under 2.4.0-test12-pre7,
glibc-2.2 both standalone and in gdb (gdb 5.0) (all tools except
kernel as of today woody). In gdb I had to do
'handle SIG32 noprint nostop pass', as by default gdb stops on SIG32
arrival...
Now it runs and runs and runs... I do not see any unreaped childrens.
After thread 100000 it finished.
Best regards,
Petr Vandrovec
vandrove@vc.cvut.cz
-
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/
next reply other threads:[~2000-12-08 20:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.BSI.4.02.10012081708350.130-100000@frogger.telerama.c om>
2000-12-08 21:21 ` Petr Vandrovec [this message]
2000-12-08 22:15 ` Pthreads, linux, gdb, oh my! (fwd) Peter Berger
2000-12-08 22:31 ` David Relson
2000-12-08 16:53 Peter Berger
2000-12-08 17:18 ` Alan Cox
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
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=F1BEC884C26@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--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