royitaqi wrote: Hi @JDevlieghere,
I think I know why: In the `Host::FindProcessImpl()` for iOS simulator, after getting all processes in the macOS, it filters out the processes which are being debugged ([here](https://fburl.com/eid5y2oa)). `a.out` is of course being debugged (by the test case) and got filtered out. IMHO this is more like a limitation of the test, not a bug in the implementation. Now, there are a few ways we can go: 1. Accept the patch as is, since we have confirmed that it's not a bug. Downside is that the test isn't super convincing. 2. If we want to make the api test to find `a.out`, we can add an additional parameter to `platform process list` (e.g. `--all-processes`) to skip such filter, then forward such parameter all the way into `Host::FindProcessImpl()`. LMK whether or not you think this would be useful besides the api test (e.g. would a user want this). 3. Instead of finding `a.out`, we can find other processes which is running on the iOS simulator because of the test. My difficult is that I don't know any of such processes. Looking forward to your thoughts. Best, Roy https://github.com/llvm/llvm-project/pull/139174 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
