HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: debugging problems
Operating System - HP-UX
1834183
Members
2621
Online
110064
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
04-04-2006 08:08 PM
04-04-2006 08:08 PM
debugging problems
11i, C8000, gcc 3.2.3, various debuggers.
Everytime my app halts for what ever reason (assert, exception, etc) while in a debugger, it can not give me a stack trace. gdb (5.3 and 6.3) says "ttrace: bad address."
adb says "can't unwind -- no_entry" when I try to do a $c command.
wdb 5.3 runs out of memory. I have a feeling this may all be a memory issue, but all my fiddling with kernel params doesn't seem to have helped.
In scanning what I've written, there's not really anything to give you much of a clue, but hopefully you've seen ttrace: Bad address before and can solve my troubles :)
thanks,
tom
Everytime my app halts for what ever reason (assert, exception, etc) while in a debugger, it can not give me a stack trace. gdb (5.3 and 6.3) says "ttrace: bad address."
adb says "can't unwind -- no_entry" when I try to do a $c command.
wdb 5.3 runs out of memory. I have a feeling this may all be a memory issue, but all my fiddling with kernel params doesn't seem to have helped.
In scanning what I've written, there's not really anything to give you much of a clue, but hopefully you've seen ttrace: Bad address before and can solve my troubles :)
thanks,
tom
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2006 08:12 PM
04-04-2006 08:12 PM
Re: debugging problems
ttrace: bad address. means.. debugger is unable to get informations from that address bcas application debugging is completed. You have to setup proper break point during debugging..
Better check memory usage as,
1) UNIX95=1 ps -ef -o sz,vsz,pid,comm
2) top
3) swapinfo -tam
4) Get informations for maxssiz,maxdsiz related setting.
--
Muthu
Better check memory usage as,
1) UNIX95=1 ps -ef -o sz,vsz,pid,comm
2) top
3) swapinfo -tam
4) Get informations for maxssiz,maxdsiz related setting.
--
Muthu
Easy to suggest when don't know about the problem!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2006 08:12 PM
04-04-2006 08:12 PM
Re: debugging problems
Hi Tom,
You can use "tusc".
http://hpux.connect.org.uk/hppd/hpux/Sysadmin/tusc-7.8/
-Arun
You can use "tusc".
http://hpux.connect.org.uk/hppd/hpux/Sysadmin/tusc-7.8/
-Arun
"A ship in the harbor is safe, but that is not what ships are built for"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-27-2006 06:10 AM
04-27-2006 06:10 AM
Re: debugging problems
I went away from this for a while, I've been using Insure++, at least it gives me a stack trace. However, eventually it runs out of memory too!
I made a little testapp to just keep malloc'ing until it fails, using decreasing amounts of memory each time.
I guess I only get one attachment, so I'll put the code in here, with my results, swapinfo, ps info, and kernel params in the attachment.
Thanks for any pointers.
#include
int main()
{
unsigned long long amount_allocated = 0;
unsigned long amount_to_allocate = 10000000;
while(true)
{
if(malloc(amount_to_allocate) != 0)
{
amount_allocated += amount_to_allocate;
}
else
{
std::cerr << "Failed to allocate " << amount_to_allocate << " bytes." << std::endl;
std::cerr << "Currently using " << amount_allocated << std::endl;
if(amount_to_allocate > 1)
amount_to_allocate /= 10;
else
{
break;
}
}
}
std::cerr << "That's all she wrote. Press any key and enter to exit." << std::endl;
char c;
std::cin >> c;
return 0;
}
I made a little testapp to just keep malloc'ing until it fails, using decreasing amounts of memory each time.
I guess I only get one attachment, so I'll put the code in here, with my results, swapinfo, ps info, and kernel params in the attachment.
Thanks for any pointers.
#include
int main()
{
unsigned long long amount_allocated = 0;
unsigned long amount_to_allocate = 10000000;
while(true)
{
if(malloc(amount_to_allocate) != 0)
{
amount_allocated += amount_to_allocate;
}
else
{
std::cerr << "Failed to allocate " << amount_to_allocate << " bytes." << std::endl;
std::cerr << "Currently using " << amount_allocated << std::endl;
if(amount_to_allocate > 1)
amount_to_allocate /= 10;
else
{
break;
}
}
}
std::cerr << "That's all she wrote. Press any key and enter to exit." << std::endl;
char c;
std::cin >> c;
return 0;
}
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