From: Dan Pop <Dan.Pop@cern.ch>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Bug report: 4-threaded program gets seg. fault on malloc, on linu x R2.4.3.
Date: Thu, 31 May 2001 04:26:56 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005674@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005668@msgid-missing>
On Fri, 25 May 2001, Robboy, David G wrote:
> I have reported this on bugzilla also, Bug #42354. I don't know whether it
> is a kernel bug, libc, or libpthread.
More likely, a problem with your system.
> The attached program spawns 3 new threads, and each of the 4 threads does a
> malloc. Run it on a 4P Lion.
> On Linux kernel R2.4.3 (Red Hat release 7.0.98), it aborts with a
> segmentation fault. The same binary executable runs correctly on a R2.4.1
> kernel.
I couldn't reproduce your problem, despite having exactly the same
hardware and software configuration:
pcpole67:~ 0 6> uname -a
Linux pcpole67 2.4.3-2.10.1smp #1 SMP Fri Apr 20 12:10:00 EDT 2001 ia64 unknown
pcpole67:~ 0 7> cat /etc/issue
Red Hat Linux release 7.0.98 (Wolverine)
Kernel 2.4.3-2.10.1smp on a 4-processor ia64
pcpole67:~ 0 8> gcc foo.c -lpthread
pcpole67:~ 0 9> ./a.out
Calling malloc: 0
Calling malloc: 3
Called malloc: 0
Called malloc: 3
Calling malloc: 1
Calling malloc: 2
Called malloc: 1
Called malloc: 2
pcpole67:~ 0 10>
The box has a vanilla Red Hat release 7.0.98 installation.
> main(argc, argv)
>
> int argc;
> char *argv;
^^^^^^^^^^
If you want to define main in this antique fashion, at least do it right.
Dan
next prev parent reply other threads:[~2001-05-31 4:26 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 ` Dan Pop [this message]
2001-05-31 5:33 ` David Mosberger
2001-06-01 8:03 ` [Linux-ia64] Bug report: 4-threaded program gets seg. fault on malloc, on linu x R2.4.3 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-105590693005674@msgid-missing \
--to=dan.pop@cern.ch \
--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 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.