From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <48241CE9.8070605@domain.hid> Date: Fri, 09 May 2008 11:44:09 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <4824197E.90709@domain.hid> <2ff1a98a0805090235t2f3c46a2vb19a4ccc7c2157b@domain.hid> <48241C06.4040105@domain.hid> In-Reply-To: <48241C06.4040105@domain.hid> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-core] [PATCH] Unfreeze timers when debugged target exits List-Id: "Xenomai life and development \(bug reports, patches, discussions\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gilles Chanteperdrix Cc: Xenomai-core@domain.hid Jan Kiszka wrote: > Gilles Chanteperdrix wrote: >> On Fri, May 9, 2008 at 11:29 AM, Jan Kiszka wrote: >>> + if (xnthread_test_info(thread, XNDEBUG)) >>> + unlock_timers(); >>> + >> Will this work if several threads are currently being debugged ? > > Not better or worse than with the current code. The whole approach is > not fixed by this patch, just some collateral damage is reduced. > > Well, maybe some counter should be used to track the number of XNDEBUG > bits in the system and unfreeze the timers when that becomes zero. Will > look into this. Correction: that counter already exists in nkpod->timerlck. So it should work even if other threads still have XNDEBUG set. Jan -- Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded Linux