Jump to content
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
HP.com home

Transition Impacts

Tru64 UNIX Software Transition Kit
» 

DSPP Home

» HP STK home
Tru64 UNIX STK
» Home
» Overview
» Tools
» Documentation
» Transition impacts
» Identifier types
» Impact list
» Porting to HP-UX
» FAQ
» Glossary
» Help
» Send us feedback
Site maps
» Tru64 UNIX STK
» DSPP
Content starts here

critical impact:

msemaphore structure - different size and alignment (CrCh107)

TH Impacts

Problem description

The size and alignment requirements for the msemaphore data structure are different on Tru64 UNIX and HP-UX.

The msemaphore structure is used by the msem_init, msem_lock, msem_unlock, and msem_remove functions to perform semaphore operations. On Tru64 UNIX, the msemaphore structure is 8 bytes; on HP-UX, 16 bytes. The HP-UX implementation also requires 16 byte alignment.

Identifiers

C/C++ Misc. Identifiersmsemaphore      

See also

Solution description

Review the applicable manpages and code.

Applications that use the msemaphore data structure might not work correctly, depending on how the structure is used. Review the applicable manpages and code to determine how to resolve the issue.

See also


Problem summary

classifications source types OS release severity type
TH C, C++ any HP-UX 11i version critical changed
Printable version
Privacy statement Using this site means you accept its terms Feedback to DSPP
© 2007 Hewlett-Packard Development Company, L.P.