| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2024-03-07 | Fix vfork test strcmp buildbot failure (#84224) | jeffreytan81 | |
| The buildbot seems to complain about `strcmp` function not available in the vfork patch (https://github.com/llvm/llvm-project/pull/81564): https://lab.llvm.org/buildbot/#/builders/68/builds/70093/steps/6/logs/stdio Unfortunately, I can't reproduce the failure on my linux machine so this is a guessing fix. If anyone has a way to reproduce and very this fix, please feel free to merge this change. Co-authored-by: jeffreytan81 <jeffreytan@fb.com> | |||
| 2024-03-06 | [lldb][test] iwyu for vfork test | Jordan Rupprecht | |
| 2024-03-06 | Fix lldb crash while handling concurrent vfork() (#81564) | jeffreytan81 | |
| We got user reporting lldb crash while the debuggee is calling vfork() concurrently from multiple threads. The crash happens because the current implementation can only handle single vfork, vforkdone protocol transaction. This diff fixes the crash by lldb-server storing forked debuggee's <pid, tid> pair in jstopinfo which will be decoded by lldb client to create StopInfoVFork for follow parent/child policy. Each StopInfoVFork will later have a corresponding vforkdone packet. So the patch also changes the `m_vfork_in_progress` to be reference counting based. Two new test cases are added which crash/assert without the changes in this patch. --------- Co-authored-by: jeffreytan81 <jeffreytan@fb.com> | |||
