public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Robboy, David G" <david.g.robboy@intel.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Seg. fault in malloc with pthreads on Red Hat R2.4.3
Date: Fri, 25 May 2001 05:27:56 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005670@msgid-missing> (raw)

A 4-threaded fft program  runs on a 4P Lion when built under Turbolinux
R2.4.1, but gets a segmentation fault in malloc when built under Red Hat
R2.4.3. 

The compiler on the system where it works is:
gcc version 2.96-ia64-000717 snap 001117
On the system where it doesn't work:
gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-81)

The program is statically linked. 
4 threads call malloc, 3 threads return from malloc and one thread gets a
seg. fault.  Gdb says the fault occurred in pthread_handle_create() and says
it was a SIGILL.

Is there something special you have to do in order to link to thread-safe
libraries, other than include "-lpthread" in the command line?

Is this a bug in Red Hat's C library?  If so, is there a way to report it to
Red Hat?

Thanks,
David Robboy



                 reply	other threads:[~2001-05-25  5:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=marc-linux-ia64-105590693005670@msgid-missing \
    --to=david.g.robboy@intel.com \
    --cc=linux-ia64@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox