| Unresponsive GDB with Memory Leak [message #1775722] |
Fri, 03 November 2017 21:36  |
Eclipse User |
|
|
|
I have an issue with debugging on eclipse. Like so many problems with debugging, if I directly use gdb everything works fine, smooth. But when trying to use the eclipse front-end, problems appear.
This particular issue causes GDB to become unresponsive and enter a busy loop, continually allocating memory without releasing it. If I leave it running for too long, it WILL take up all available memory on my machine. I don't know what's causing it... This is a fresh install of linux, and hence, also a fresh install of eclipse and gdb. This is the latest package of both applications. Reinstalls have not been done, but if someone thinks it will help, I will try it.
If anyone has any suggestions, I'm willing to try them out.
Note:
This is Eclipse Oxygen 4.7.1a running on Arch Linux Kernel version 4.13.11-1 x86_64
|
|
|
|
| Re: Unresponsive GDB with Memory Leak [message #1804124 is a reply to message #1803984] |
Mon, 18 March 2019 23:45  |
| Eclipse User |
|
|
|
Frustrating and hard to track down.
You haven't given enough information to be sure but guessing ...
Likely it's because CDT is interrogating GDB to fill in the Variables View.
Has happened to me -- more than once.
Can happen if you have a large variable often a vector or array.
Or a particularly complicated one (std::list<T>, std::set<T>, etc., or even T, where T is not a simple class)
I've also encountered problems with uninitialized lists, sets and maps until fully initialized.
If you have a lot of variables in scope, try reducing them.
Use the Expressions View to observe only those variables of interest
or only some elements.
You may need to close the Variables View.
Sometimes the solution is to not single step through the code and use alternate means of debugging (like print statements).
[Updated on: Tue, 19 March 2019 05:39] by Moderator |
|
|
Powered by
FUDForum. Page generated in 0.02771 seconds
Home