KLapshin added a comment. In http://reviews.llvm.org/D12968#256563, @labath wrote:
> This is definitely not a proper fix for this problem, it merely sweeps the > problem under the carpet. If something like this makes a difference then it > means something has gone horribly wrong a long time ago. I haven't been able > to reproduce this locally, but I'd recommend trying to set up some > memory-allocation/thread-race checker and see what it produces. > > I still think the original solution of hijacking the listener was correct, > but we need to figure out what is the right point at which to hijack it. I'll > try to look into this when I get a bit of time. @labath, Yes, I even noticed what latest "fix" patch is just hint to fact what whole Process m_listener object looks like freed or unitialized memory - m_events collection size in Listener before crash happened looks invalid absolutely - random value, in my case about 8 millions events (!). This looks about threads race condition, so still investigating - slow because bit bust with other issues, excuse me. Repository: rL LLVM http://reviews.llvm.org/D12968 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
