Re: Thread safe malloc in Tru64?
From: Jerry Feldman (gaf-noSPAM_at_blu.org)
Date: 11/20/03
- Previous message: Eduardo: "snmp subagents development"
- In reply to: Ioannis E. Venetis: "Thread safe malloc in Tru64?"
- Next in thread: David Butenhof: "Re: Thread safe malloc in Tru64?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 20 Nov 2003 16:30:31 GMT
On Thu, 20 Nov 2003 16:11:01 +0200
"Ioannis E. Venetis" <iev@hpclab.ceid.upatras.gr> wrote:
> Hello,
>
> I am trying to create a library that will run, among other
> architectures, on Tru64/Alpha systems.
> Of course, this library has a machine independant (the same for all
> architectures) and a machine
> dependant part. For some reasons, I chose to use the
> thread_create/thread_get_state/
> thread_set_state/thread_resume/thread_terminate interface in the
> machine dependant part of the
> library to manage kernel-level threads on Tru64 Unix systems. I am
> mentioning it in case this has
> something to do with the problem I will describe.
While I am not purporting to solve your problem, but all libc functions,
including malloc(3), were made threadsafe (I believe) as of Tru64
(Digital Unix) 4.0.
When compiling use -pthread rather than -lpthread or -lpthreads.
Additionally, libc_r is nothing more than a symlink to libc.
Also be aware that the Tru64 thread package uses a combination of kernel
threads and user threads.
Try using HP's native compiler for your testing. Part of your problem
might be that gcc 2.95 is out of date.
-- Jerry Feldman <gaf-nospam-at-blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
- Previous message: Eduardo: "snmp subagents development"
- In reply to: Ioannis E. Venetis: "Thread safe malloc in Tru64?"
- Next in thread: David Butenhof: "Re: Thread safe malloc in Tru64?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
