- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Huge stack segment sizes with aCC 3.13
Operating System - HP-UX
1752647
Members
5932
Online
108788
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
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
тАО05-29-2001 07:59 PM
тАО05-29-2001 07:59 PM
Huge stack segment sizes with aCC 3.13
Hi,
I am experiencing a problem with large process size. I have identified that the stack segment grows by hundreds of MB, for no apparent reason.
I have tried to reproduce this in an example prog without success.
Has anyone seen this kind of behaviour before?
Thanks,
S.
I am experiencing a problem with large process size. I have identified that the stack segment grows by hundreds of MB, for no apparent reason.
I have tried to reproduce this in an example prog without success.
Has anyone seen this kind of behaviour before?
Thanks,
S.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-30-2001 05:46 AM
тАО05-30-2001 05:46 AM
Re: Huge stack segment sizes with aCC 3.13
Hi,
No, I haven't seen that behavior but if I had to guess, I would suspect unchecked recursion.
Especially if you a function with a large chunk of local variables which would be allocated off the stack. My first cut at this would be to do a stack trace. Hopefully, you will see the same function or a pair of mutually recursive functions called over and over.
Good Hunting, Clay
No, I haven't seen that behavior but if I had to guess, I would suspect unchecked recursion.
Especially if you a function with a large chunk of local variables which would be allocated off the stack. My first cut at this would be to do a stack trace. Hopefully, you will see the same function or a pair of mutually recursive functions called over and over.
Good Hunting, Clay
If it ain't broke, I can fix that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-30-2001 02:47 PM
тАО05-30-2001 02:47 PM
Re: Huge stack segment sizes with aCC 3.13
Hi,
I've thought of one more thing to look for:
Local for 1 VERY LARGE local variable like an
array with a few extra zero's in declaration or if you are using #defines one slightly 'improved' value, e.g what was
#define MY_SIZE 0x5000 becomes 0xff5000.
The fact that you can't re-create the problem plus the fact that I can't do it either unless I resort to one of the two methods (recursion or bad declaration) above indicates that it probably is not a systemic problem with the compiler/linker.
I'm surprised that you have such a maxssiz, I prefer to keep mine much smaller so that problems like this appear much sooner.
More food for thought, Clay
I've thought of one more thing to look for:
Local for 1 VERY LARGE local variable like an
array with a few extra zero's in declaration or if you are using #defines one slightly 'improved' value, e.g what was
#define MY_SIZE 0x5000 becomes 0xff5000.
The fact that you can't re-create the problem plus the fact that I can't do it either unless I resort to one of the two methods (recursion or bad declaration) above indicates that it probably is not a systemic problem with the compiler/linker.
I'm surprised that you have such a maxssiz, I prefer to keep mine much smaller so that problems like this appear much sooner.
More food for thought, Clay
If it ain't broke, I can fix that.
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