- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Could Memory corruption happen in HPUX10.0
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
тАО01-12-2009 07:01 AM
тАО01-12-2009 07:01 AM
Could Memory corruption happen in HPUX10.0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2009 07:54 AM
тАО01-12-2009 07:54 AM
Re: Could Memory corruption happen in HPUX10.0
Hardware memory corruptions usually are captured at the hardware level as single bit errors or page deallocation tables.
What memory mechanism do you use to exchange the data?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2009 08:11 AM
тАО01-12-2009 08:11 AM
Re: Could Memory corruption happen in HPUX10.0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2009 08:27 AM
тАО01-12-2009 08:27 AM
Re: Could Memory corruption happen in HPUX10.0
Use cstm or mstm or xstm if part of the OS to physically test memory.
If it checks out without problem, then begin to suspect your software is a contributing factor.
You could have some pointer or other programming problems creating the core dump.
To answer your question, yes, memory corruption is possible, but if you can not independently create the problem without your software, then suspect your software.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2009 08:36 AM
тАО01-12-2009 08:36 AM
Re: Could Memory corruption happen in HPUX10.0
Do you always get the "DES..." changed to "FES..."? The reason I asked was that there is no guarantee that you will get the same exact memory hardware address each time you run the two processes. If that's the case most likely it is not hardware related.
What does "file core" show as the reason for the core dump?
> it never had an issue for 15 years but it started recently and nothing new has come up or changed...
When something like this happens without any system changes it is usually data related, a data type changed or a threshold was exceeded or something within the data itself.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2009 10:46 AM
тАО01-12-2009 10:46 AM
Re: Could Memory corruption happen in HPUX10.0
Not like that actually sometimes the first character is replaced by F ,otherwise more than one character but always the starting character is replaced by F.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2009 10:49 AM
тАО01-12-2009 10:49 AM
Re: Could Memory corruption happen in HPUX10.0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2009 03:29 PM
тАО01-12-2009 03:29 PM
Re: Could Memory corruption happen in HPUX10.0
>buffer, which is then picked up by another process.
Please be more specific. Is this shared memory or a mapped file?
What are you using for synchronization?
>Also the second process core dumps.
Is this related to the corrupted string or something else?
>tried to use GDB but could not get the stack trace.
What did you get instead? What version of gdb do you have?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2009 10:01 PM
тАО01-12-2009 10:01 PM
Re: Could Memory corruption happen in HPUX10.0
What are you using for synchronization?
> it is shared memory
Is this related to the corrupted string or something else?
> I think yes .. the second process just logs the data it retrieves using pointers to generate a report , now the data is picked up from shared memory put in by the first process
What did you get instead? What version of gdb do you have?
> got nothing actually , we used the debug executable and tried to use gdb and adb to debug, but we got ????? in place of function names , in adb we got something like stack could not be unwind . Everything is outdated , like you said the OS too , gdb version is HP gdb 1.1 and i cannot update it too ....so only have to use what I have
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2009 10:56 PM
тАО01-12-2009 10:56 PM
Re: Could Memory corruption happen in HPUX10.0
The oldest WDB archive is 5.0 for 11.00.
You might be able to copy the corefile, executable and all of the shlibs and dld.sl to a 11.11 box and debug?