[Lldb-commits] [PATCH] Avoid leakage of file descriptors in LLDB and LLGS

Zachary Turner zturner at google.com
Tue Feb 3 08:37:26 PST 2015


This doesn't seem like the best way for the test to do this. I don't know
much about linux, but windows at least we can just have the debugger
directly figure out how many handles are open in the target process. And
this is a pretty useful thing to be able to do in a debugger, for example
if you're debugging a handle leak.

Is this not possible on linux? If it is, it would be much better to just
have the debugger enumerate the target's handles and verify there are only 3
On Tue, Feb 3, 2015 at 8:15 AM Pavel Labath <labath at google.com> wrote:

> Update main.c: remove tabs
>
>
> http://reviews.llvm.org/D7372
>
> Files:
>   source/Plugins/Process/Linux/NativeProcessLinux.cpp
>   source/Plugins/Process/Linux/ProcessMonitor.cpp
>   source/Target/ProcessLaunchInfo.cpp
>   test/dosep.py
>   test/functionalities/avoids-fd-leak/Makefile
>   test/functionalities/avoids-fd-leak/TestFdLeak.py
>   test/functionalities/avoids-fd-leak/main.c
>
> EMAIL PREFERENCES
>   http://reviews.llvm.org/settings/panel/emailpreferences/
> _______________________________________________
> lldb-commits mailing list
> lldb-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-commits
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-commits/attachments/20150203/e54d367e/attachment.html>


More information about the lldb-commits mailing list