All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: PARISC list <parisc-linux@lists.parisc-linux.org>,
	John David Anglin <dave.anglin@nrc-cnrc.gc.ca>,
	Randolph Chung <tausq@debian.org>
Subject: Re: [parisc-linux] pthread attributes and stack positions (gcc related?)
Date: Mon, 29 Sep 2003 15:02:51 -0400	[thread overview]
Message-ID: <20030929190251.GB21914@systemhalted> (raw)
In-Reply-To: <20030929151038.GC15180@systemhalted>

On Mon, Sep 29, 2003 at 11:10:38AM -0400, Carlos O'Donell wrote:
> I agree, it seems though that after "fork" the values returned by 
> "pthread_getattr_np (pthread_self (), &a);" are bogus. While if you call
> pthread_create(...) and then the previous line from within the newly
> created thread the values are initialized properly. A mistake might
> exist with symbol versioning by which we are not calling libpthread's
> overloaded thread manager "fork()" and continuing on with the normal syscall.

Looking closer there is a __libc_maybe_call2 that happens during a fork
that is called and libpthread is linked. The maybe call tries to see if
pthread_fork is available, if it doesn't see a valid symbol it just
calls ARCH_FORK(). This looks like a suspect. So do a number of the
#ifdef's in pthread.c

c.

      reply	other threads:[~2003-09-29 19:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-28 17:42 [parisc-linux] pthread attributes and stack positions (gcc related?) Carlos O'Donell
2003-09-28 17:53 ` James Bottomley
2003-09-29 15:10   ` Carlos O'Donell
2003-09-29 19:02     ` Carlos O'Donell [this message]

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=20030929190251.GB21914@systemhalted \
    --to=carlos@baldric.uwo.ca \
    --cc=James.Bottomley@steeleye.com \
    --cc=dave.anglin@nrc-cnrc.gc.ca \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=tausq@debian.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.