Re: [cdt-dev] Debug CDT file resource leaks

[Jonah Graham <jonah@xxxxxxxxxxxxxxxx>]

Hello Simeon,

(I missent this earlier and it bounced - in the meantime I you have created a bug report and possible fix - thank you! - I am resending the below as it may provide useful.)

What I would recommend is using https://file-leak-detector.kohsuke.org/ to see if you can identify the culprit of who is keeping the file handle open. I don't see any files (as reported by the detector) being left open when I have an so in my project and I delete the project.

Thanks

Jonah

~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com

On Mon, 2 Dec 2019 at 09:05, Christian Walther <walther@xxxxxxxx> wrote:

Simeon Andreev wrote:
> Is there any tracing option that I can use, to find out which code opens/locks the .so files? Or is there an alternative to tracing?

I don't have any generic debugging advice, but my first suspicion is that it might be a binary parser. If this is a managed project that has this setting, try going to Project Properties > C/C++ Build > Settings > Binary Parsers and disabling everything. See if that makes the symptom go away. If so, that doesn't solve the problem, but you know where to look more closely.

(We disabled the ELF parser in our toolchain definition because it annoyed us for other reasons.)

 -Christian

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev