- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- ERROR MESSAGE : Cannot access memory at address 0x...
Operating System - HP-UX
1821250
Members
3061
Online
109632
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
Discussions
Forums
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
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
тАО12-02-2002 10:39 PM
тАО12-02-2002 10:39 PM
ERROR MESSAGE : Cannot access memory at address 0x3f 5d0268; Language : C++
Hi wizards,
We have a Wireless application [GSM] in which we have wriiten the code in C++ Lang on a HP-UX 10.20 platform and the Target HP Hardware is N-Class servers.
It's been reported that our application is coring sometimes.
And from the gdb traces, we see a line as:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Cannot access memory at address 0x3f 5d0268" and then it gets killed in malloc...
Please help me out in this regard.
Thanks in Advance,
Arun Kumar
Bangalore, INDIA.
We have a Wireless application [GSM] in which we have wriiten the code in C++ Lang on a HP-UX 10.20 platform and the Target HP Hardware is N-Class servers.
It's been reported that our application is coring sometimes.
And from the gdb traces, we see a line as:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Cannot access memory at address 0x3f 5d0268" and then it gets killed in malloc...
Please help me out in this regard.
Thanks in Advance,
Arun Kumar
Bangalore, INDIA.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-03-2002 12:06 AM
тАО12-03-2002 12:06 AM
Re: ERROR MESSAGE : Cannot access memory at address 0x3f 5d0268; Language : C++
Arun,
are you sure you have 1GB of the main memory and at this location (0x3f5d0268=1,063,060,072) server does not have memory hole, ROM or any other locked area? If your server is out-of-memory then consider (at least try) to add more
Eugeny
are you sure you have 1GB of the main memory and at this location (0x3f5d0268=1,063,060,072) server does not have memory hole, ROM or any other locked area? If your server is out-of-memory then consider (at least try) to add more
Eugeny
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-03-2002 05:05 AM
тАО12-03-2002 05:05 AM
Re: ERROR MESSAGE : Cannot access memory at address 0x3f 5d0268; Language : C++
Hi.
What does exactly backtrace of the stack, when your process gets killed inside malloc? What signal kills the process?
If it's from malloc my first guess is that you corrupt memory somewhere. Try to use a tool to trace memory allocations and overwriting. Perheps you are using freed memory, or write after / before allocated block, corrupting malloc's free list.
Good luck
Adam
What does exactly backtrace of the stack, when your process gets killed inside malloc? What signal kills the process?
If it's from malloc my first guess is that you corrupt memory somewhere. Try to use a tool to trace memory allocations and overwriting. Perheps you are using freed memory, or write after / before allocated block, corrupting malloc's free list.
Good luck
Adam
I do everything perfectly, except from my mistakes
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.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP