Date: Mon, 25 May 2009 14:34:10 +0200 From: =?UTF-8?Q?Nikola_Kne=C5=BEevi=C4=87?= <laladelausanne@gmail.com> To: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Problem with LOCK_PROFILING stats in 7.2 Message-ID: <0829C953-67AA-42DB-BCDF-B294F2E39618@gmail.com> In-Reply-To: <10A866FD-3D61-418E-8871-5C60159CEB6C@gmail.com> References: <10A866FD-3D61-418E-8871-5C60159CEB6C@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 05.22.2009, at 14:21 , Nikola Kne=C5=BEevi=C4=87 wrote: > I'm using LOCK_PROFILING to, well, profile some locks in the module =20= > I'm working on. I also have INVARIANTS turned on. Numbers I'm =20 > getting look correct, however, name of the lock is strange (for some =20= > of the locks I'm using): > > 25725 51777294 10979957 7331938 7 1 =20 > 408303 896814 /home/knl/work/mx/click/bsdmodule/..//include/=20 > click/sync.hh:395 (sleep mutex:?? ?????Yf;??????? ?????=12?:?????=18=03)= > > Why am I getting this instead of lock's real name: MasterLock[10060]? To reply to myself :) mtx_init & co. expects the name to be persistent during the whole run. =20= So, never pass values from the stack to it, as I did. Cheers, Nikola=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0829C953-67AA-42DB-BCDF-B294F2E39618>