HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Method free of aCC ...
Operating System - HP-UX
1832420
Members
3229
Online
110042
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
Forums
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
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
05-26-2003 01:32 AM
05-26-2003 01:32 AM
Method free of aCC ...
Sometimes, My application crashes when method free of file /opt/aCC/include/memory is called ...
i a not sure that the problem comes from my application ...
Do you know if aCC should be compiled with specific flags when application is a multi-thread application ... (because i saw in file memory where source of operation free and delete are defined , that flags for multi-thread exist ...
i a not sure that the problem comes from my application ...
Do you know if aCC should be compiled with specific flags when application is a multi-thread application ... (because i saw in file memory where source of operation free and delete are defined , that flags for multi-thread exist ...
yop
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-26-2003 02:33 AM
05-26-2003 02:33 AM
Re: Method free of aCC ...
Hi
I have a bad news for you.
Crashes during free() 99,9% comes from bug in a program, but most frequently from very differenty place. In other words you write under address you shouldnt use, and therefore corrupt the memory. When you call free() this corruption jumps out of the box. The other reason may be calling free() with bad address - freeing memory twice for example, but these are relatively easy to catch.
The other info I can give you is that:
operators new and delete are implemented as calls to malloc() and free() (however _do_not_ use free() for memory allocated with new, of course).
malloc() and free() are implemented to be multithread safe (the use internal mutex to protect data consistency, if you're interested), so there is no need to check these flags at compile time for them.
Good luck
Adam
I have a bad news for you.
Crashes during free() 99,9% comes from bug in a program, but most frequently from very differenty place. In other words you write under address you shouldnt use, and therefore corrupt the memory. When you call free() this corruption jumps out of the box. The other reason may be calling free() with bad address - freeing memory twice for example, but these are relatively easy to catch.
The other info I can give you is that:
operators new and delete are implemented as calls to malloc() and free() (however _do_not_ use free() for memory allocated with new, of course).
malloc() and free() are implemented to be multithread safe (the use internal mutex to protect data consistency, if you're interested), so there is no need to check these flags at compile time for them.
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
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP