public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Bug report: 4-threaded program gets seg. fault on malloc, on linu
Date: Thu, 31 May 2001 05:33:03 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005677@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005668@msgid-missing>

>>>>> On Fri, 25 May 2001 16:17:37 -0700, "Robboy, David G" <david.g.robboy@intel.com> said:

  David.R> I have reported this on bugzilla also, Bug #42354.  I don't
  David.R> know whether it is a kernel bug, libc, or libpthread.  The
  David.R> attached program spawns 3 new threads, and each of the 4
  David.R> threads does a malloc.  Run it on a 4P Lion.  On Linux
  David.R> kernel R2.4.3 (Red Hat release 7.0.98), it aborts with a
  David.R> segmentation fault.  The same binary executable runs
  David.R> correctly on a R2.4.1 kernel.

You didn't say how you compiled the program.  Let's assume you used
"gcc -O2 -pthread": for what it's worth, this works fine here, both on
Wolverine and Guinness.  In both cases with kernel 2.4.4 and on
Wolverine I'm using glibc-2.2.2-10.

	--david


  parent reply	other threads:[~2001-05-31  5:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-25 23:17 [Linux-ia64] Bug report: 4-threaded program gets seg. fault on malloc, on linu Robboy, David G
2001-05-31  4:26 ` [Linux-ia64] Bug report: 4-threaded program gets seg. fault on malloc, on linu x R2.4.3 Dan Pop
2001-05-31  5:33 ` David Mosberger [this message]
2001-06-01  8:03 ` Andreas Schwab

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-105590693005677@msgid-missing \
    --to=davidm@hpl.hp.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