- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Leaks in mainThread()
Operating System - HP-UX
1753637
Members
5619
Online
108798
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
тАО11-30-2010 10:10 PM
тАО11-30-2010 10:10 PM
Leaks in mainThread()
Hi,
I am new to GDB(version 6.1). I would like to know about some errors like when I am finding memory leaks through gdb I am only getting the results like:-
20 bytes leaked in 1 blocks
No. Total bytes Blocks Address Function
0 20 1 0x4106c310 mainThread()
And :-
20 bytes leaked at 0x4106c310 (100.00% of all bytes leaked)
#0 0x200000007e8280d2 in mainThread() at ../cm_main.c:4258
#1 0x04000bc2 in main() at cm.cpp:22
#2 0x60000000c00427b2 in main_opd_entry() from /usr/lib/hpux32/dld.so
which I think cannot be possible or may be it is not finding the leaks at all and stuck at some point.
If anybody come across such issues please help me out.
thanks
MJ
I am new to GDB(version 6.1). I would like to know about some errors like when I am finding memory leaks through gdb I am only getting the results like:-
20 bytes leaked in 1 blocks
No. Total bytes Blocks Address Function
0 20 1 0x4106c310 mainThread()
And :-
20 bytes leaked at 0x4106c310 (100.00% of all bytes leaked)
#0 0x200000007e8280d2 in mainThread() at ../cm_main.c:4258
#1 0x04000bc2 in main() at cm.cpp:22
#2 0x60000000c00427b2 in main_opd_entry() from /usr/lib/hpux32/dld.so
which I think cannot be possible or may be it is not finding the leaks at all and stuck at some point.
If anybody come across such issues please help me out.
thanks
MJ
- Tags:
- leak
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-01-2010 11:17 AM
тАО12-01-2010 11:17 AM
Re: Leaks in mainThread()
What is is doing on line 4258 of cm_main.c?
Do you ever free that space?
Do you ever free that space?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-02-2010 02:41 AM
тАО12-02-2010 02:41 AM
Re: Leaks in mainThread()
cm is an executable. we do not have the source code for cm_main.c.
But we have shared object(.so) files linked to cm.
These .so files contain custom API's
These API are invoked using custom workbenches(you can say dlopen)
We are able to successfully set the breakpoints within this API.
Sometimes the leaks are captured within this custom API's
But sometimes it goes to the cm_main.c and captures the above leaks(100% leak in mainThread()) and does not scan the API at all
Why is it so inconsistent?
But we have shared object(.so) files linked to cm.
These .so files contain custom API's
These API are invoked using custom workbenches(you can say dlopen)
We are able to successfully set the breakpoints within this API.
Sometimes the leaks are captured within this custom API's
But sometimes it goes to the cm_main.c and captures the above leaks(100% leak in mainThread()) and does not scan the API at all
Why is it so inconsistent?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-02-2010 11:19 PM
тАО12-02-2010 11:19 PM
Re: Leaks in mainThread()
>But sometimes it goes to the cm_main.c and captures the above leaks (100% leak in mainThread()) and does not scan the API at all
Why is it so inconsistent?
I'm not sure how that can happen. The allocation site for memory should be very accurate. There should be a call to malloc at cm_main.c:4258. Perhaps sometimes this is freed by a call inside your API?
Why is it so inconsistent?
I'm not sure how that can happen. The allocation site for memory should be very accurate. There should be a call to malloc at cm_main.c:4258. Perhaps sometimes this is freed by a call inside your API?
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