Remove the thread name caching code. It does not handle the possibility
of thread name changing between requests, therefore breaking
TestGdbRemoteThreadName. While technically we could cache the results
and reset the cache on resuming process, the gain from doing that
does not seem worth the effort.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
Yes. However, their logic is simpler (it boils down to opening a dedicated file in procfs (i.e. they don't have to iterate over all threads). Nevertheless, I don't think this is called frequently enough to justify optimization at this point.