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:

mmap - some flags not available (CrUn216)

KN Impacts

Problem description

The following mmap flags either do not exist on HP-UX or have different semantics than the those on Tru64 UNIX:

  • MAP_UNALIGNED and MAP_INHERIT flags exist on Tru64 UNIX but not on HP-UX.

  • MAP_FIXED has different syntax.

On Tru64 UNIX, the flags have the following meaning:

  • MAP_UNALIGNED - Does not verify that the file offset is page aligned.

  • MAP_INHERIT - Region is not mapped by an exec call.

  • MAP_FIXED - Places a region at a fixed address.

On HP-UX, the MAP_FIXED flag means to interpret the addr parameter exactly.

Identifiers

C/C++ Misc. IdentifiersMAP_FIXED C/C++ Misc. IdentifiersMAP_INHERIT C/C++ Misc. IdentifiersMAP_UNALIGNED

See also

Solution description

Review the source code and make the following modifications:

  • If your code uses the MAP_UNALIGNED flag, you must ensure that the file offset is page aligned. On Tru64 UNIX, the mmapped region does not need to be page aligned.

  • If your code uses the MAP_INHERIT flag, you must ensure that the exec application calls mmap to map the file.

  • If your code uses the MAP_FIXED flag, you must supply a virtual address to which you will be mapped. On Tru64 UNIX, if you pass a NULL address, a virtual address is assigned by the system.

See also


Problem summary

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