I wrote a new memory allocation function to replace the glibc malloc() in
solaris 10.
It compiles well, but when I try to run it, I get the following message:
*** libc thread failure: _thread_setschedparam_main() fails
I've traced the program and found the error occurs at
On 03/19/11 08:33 PM, dengning wrote:
I wrote a new memory allocation function to replace the glibc malloc() in
solaris 10.
(Open)Solaris does not use glibc.
There are a number of alternative allocators provided (libumem for
example), do any of these meet your needs?
--
Ian.
Actually, I am writing a new spm_malloc() interface for some academic
research reason. The spm_malloc() is going to allocate a small on-chip
memory for multicore.
it looks like: void *spm_malloc(long bytes), I test the function in many
programs, it works ok.
In this example, the malloc() is
I always install GRUB on the Solaris partition, never on MBR - because if there
is a problem with GRUB, it is just a matter of activating the Solaris
partition.
If I install GRUB on MBR and if there is a problem, I have to reinstall GRUB,
fix the configuration file, etc - much more work. It
Date: Sat, 19 Mar 2011 16:32:53 +0800
From: ??dunning2...@gmail.com
To: Ian Collinsi...@ianshome.com,
opensolaris-discuss@opensolaris.org
Subject: Re: [osol-discuss] libc thread failure:
_thread_setschedparam_main() fails
Message-ID:
Hi all,
Things have been going pretty well with my home fileserver, but recently
and I think increasingly, the system is dropping off the network for
just long enough to disrupt connections.
It only really happens when copying large amounts of data, for example
an 8 gig folder of mixed file
What model motherboard are you using? I suspect it's probably a nic driver
issue.
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
struct queue *chunk_que;
chunk_que = spm_normal_malloc(sizeof(struct queue) * nqueues);
pthread_mutex_init(que-mutex, NULL);
pthread_mutex_lock(que-mutex); //The error occurs here!
Go check your test program. It is not doing what you think it is.
Check the return code from your call to
