Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Jun Sun <jsun@mvista.com>
Cc: Ralf Baechle <ralf@oss.sgi.com>, linux-mips@oss.sgi.com
Subject: Re: pthread_create() gets BUS ERROR
Date: Tue, 24 Oct 2000 03:37:43 +0200	[thread overview]
Message-ID: <20001024033743.B2816@bacchus.dhis.org> (raw)
In-Reply-To: <39F4E4C2.A9570003@mvista.com>; from jsun@mvista.com on Mon, Oct 23, 2000 at 06:24:18PM -0700

On Mon, Oct 23, 2000 at 06:24:18PM -0700, Jun Sun wrote:

> Since Ralf has not posted his patch for glibc yet, I looked into the
> problem a little bit more.

If you'd be waiting just a few minutes longer I'd have announced it :-)

The srpm is currently uploading to oss.sgi.com:/pub/linux/mips/glibc/
srpms/glibc-2.0.6-7lm.src.rpm.  The file is 4682466 bytes long, so don't
start downloading before it's completly uploaded :-)

> It appears to be another toolchain related problem, instead of a glibc
> problem.
> 
> In linuxthread/pthread.c:pthread_initialize_manager(), it accesses a
> global variable __pthread_initial_thread_bos in pthread shared library. 
> Apparently the code finds out the address of the variable through some
> table (why is that?).  It looks like the offset for variable is off by
> 8.  Another ld problem?
> 
> I am using the "old but stable" toolchains, as I stated in an earlier
> email.:-9

This description somehow rings a bell.  I'll dig through my mailfolders
and will post if I find something.

  Ralf

  reply	other threads:[~2000-10-24  1:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-19 22:31 pthread_create() gets BUS ERROR Jun Sun
2000-10-19 22:39 ` Ralf Baechle
2000-10-19 23:00   ` Jun Sun
2000-10-24  1:24   ` Jun Sun
2000-10-24  1:37     ` Ralf Baechle [this message]
2000-10-24 21:36       ` Jun Sun

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=20001024033743.B2816@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=jsun@mvista.com \
    --cc=linux-mips@oss.sgi.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