mgorny added a comment. In D116255#3213612 <https://reviews.llvm.org/D116255#3213612>, @labath wrote:
> That would deal with the code coverage, but it still leaves us with a fairly > large core file, and a lot of uninteresting tests obscuring the output. > > How do you generate these core files? Do you actually create a fresh core > dump or you just recompute the "interesting" portions from a master file you > have around? If you make the changes the the master core file, then they > would get automatically picked up during the recomputation. I do recompute them from master copies (which I finally need to upload somewhere) but the recomputation is really dumb and unaware of the file format. I suppose I could just hack LLDB to stop after grabbing the first N threads but… the first non-dump on-CPU thread is no. 200. Finishing on that will probably make the core smaller but not sure how much smaller. I'll try in a minute. > Alternatively, maybe there is a way to capture a core file without so many > processes. Either killing off everything before the core file is written, or > by making sure the other processes are never started (something like > `init=/bin/bash` on linux)? The vast majority of threads are kernel threads. At a quick glance, only about 20 threads look like userspace. CHANGES SINCE LAST ACTION https://reviews.llvm.org/D116255/new/ https://reviews.llvm.org/D116255 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
