|
From: Julian S. <js...@ac...> - 2010-10-24 10:23:25
|
> I understood that the univ_laog is used for producing the lock order > checks. (laog seems to be Lock Acquisition Order Graph). > > So, I tried --track-lockorders=no, but that seems to only disable the > reporting of lock order errors, not the building of the data structure. Hmm, can you file a bug report? This is something that should be fixed. > Is it normal that the lock acquisition graph becomes so huge ? > (at first sight, I would expect such a graph to not be *that* huge). Hmm, I'm not sure without further analysis. It might happen if your program has a large number of locks at different addresses and it locks them in a large number of different orders. > If it is normal that this graph can become huge, I can try to avoid > building this graph when --track-lockorders=no is given. > but that assumes that the univ_laog data structure is only useful for > track-lockorders. That sounds like a reasonable assumption. > So, is univ_laog only used for track-lockorders=yes ? I think so, yes. > Or is this univ_laog needed for something else in helgrind ? No. You should be able to disable its construction completely. J |