- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- nlist issue in 5.1a
Operating System - Tru64 Unix
1753818
Members
8436
Online
108805
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2003 05:53 AM
06-12-2003 05:53 AM
nlist issue in 5.1a
We have recently upgraded from 4.0f to 5.1a. I have a program that uses nlist to obtain an address for the "machine_slot" symbol in the vmunix image. This worked fine under 4.0f, but under 5.1a the machine_slot symbol can not be located. Has this symbol name been changed? Is there another symbol I should be referencing instead? Any help would be greatly appreciated.
Thanks
Thanks
- Tags:
- nlist
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2003 06:29 AM
06-12-2003 06:29 AM
Re: nlist issue in 5.1a
The machine_slot structure is gone in 5.x.
Try the processor_ptr[cpu_number] instead.
In V4, "machine_slot" is a _global_ symbol that can be used to directly
access all of the "per-cpu" machine slots, by casting it as an array and
indexing into it by cpu-number... ie: machine_slot[cpu_number].
In V5, "machine_slot" has been moved into the "processor" structure
(struct processor). It can be obtained readily, but not by the old V4
mechanism of using the global "machine"slot" variable. To get the
machine_slot structure for each processor in V5, use the global symbol
"processor_ptr" as an array, and index into it bu cpu-number; then, look
at the element "m", which is cast as a pointer to the per-cpu "struct
machine_slot"
(Eg: processor_ptr[cpu_number].m)
Hope this helps,
Christian Klein
HP Tru64 Unix Support
Try the processor_ptr[cpu_number] instead.
In V4, "machine_slot" is a _global_ symbol that can be used to directly
access all of the "per-cpu" machine slots, by casting it as an array and
indexing into it by cpu-number... ie: machine_slot[cpu_number].
In V5, "machine_slot" has been moved into the "processor" structure
(struct processor). It can be obtained readily, but not by the old V4
mechanism of using the global "machine"slot" variable. To get the
machine_slot structure for each processor in V5, use the global symbol
"processor_ptr" as an array, and index into it bu cpu-number; then, look
at the element "m", which is cast as a pointer to the per-cpu "struct
machine_slot"
(Eg: processor_ptr[cpu_number].m)
Hope this helps,
Christian Klein
HP Tru64 Unix Support
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP