From: Jun Sun <jsun@mvista.com>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: pthread_create() gets BUS ERROR
Date: Mon, 23 Oct 2000 18:24:18 -0700 [thread overview]
Message-ID: <39F4E4C2.A9570003@mvista.com> (raw)
In-Reply-To: 20001020003946.E20887@bacchus.dhis.org
Ralf Baechle wrote:
>
> On Thu, Oct 19, 2000 at 03:31:54PM -0700, Jun Sun wrote:
>
> > I am running a simple pthread_create() test. The thread gets created,
> > but the creating thread gets BUS error after the function call. In
> > fact, it gets SIGUSR1 signal. Does anybody know what is wrong here?
> >
> > It looks to me that creating thread is waiting for the created thread to
> > start up, but somehow did not install the signal handler correctly!?
> >
> > I am running with the "stable" toolchain that I generated recently,
> > i.e., binutil 2.8.1, egcs 1.0.3a and glibc2.0.6.
>
> Which libc release exactly?
>
> I've uploaded another release glibc-2.0.6-7lm to oss:/pub/linux/mips/glibc/.
> In case you're running big endian, could you try that release?
>
> (Sorry, no source, will upload the srpm tomorrow.)
>
> Ralf
Since Ralf has not posted his patch for glibc yet, I looked into the
problem a little bit more.
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
Jun
======
"...
I finally settled down with the old but deemed reliable versions :
a) binutils v2.8.1 + mips patch
ftp://sourceware.cygnus.com/pub/binutils/releases/
ftp://oss.sgi.com/pub/linux/mips/binutils/binutils-2.8.1-3.diff.gz
b) egcs 1.0.3a + mips patch
ftp://ftp.mvista.com/pub/Area51/mips_le/misc/egcs-1.0.3a.tar.gz
ftp://oss.sgi.com/pub/linux/mips/egcs/egcs-1.0.3a-2.diff.gz
c) glibc 2.0.6 + mips patch
ftp://oss.sgi.com/pub/linux/mips/glibc/srpms/glibc-2.0.6-5lm.src.rpm
..."
next prev parent reply other threads:[~2000-10-24 1:22 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 [this message]
2000-10-24 1:37 ` Ralf Baechle
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=39F4E4C2.A9570003@mvista.com \
--to=jsun@mvista.com \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@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