From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Marcel Holtmann To: BlueZ development In-Reply-To: <447F71B5.8060905@xmission.com> References: <70DCB28C5BB04A4BBB1C8512589BAC65D4F2D8@MAIL006.mail.lan> <1149202516.32406.0.camel@localhost> <447F71B5.8060905@xmission.com> Date: Fri, 02 Jun 2006 01:11:34 +0200 Message-Id: <1149203494.32406.3.camel@localhost> Mime-Version: 1.0 Subject: Re: [Bluez-devel] Strange behaviour Reply-To: BlueZ development List-Id: BlueZ development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Sender: bluez-devel-bounces@lists.sourceforge.net Errors-To: bluez-devel-bounces@lists.sourceforge.net Hi Brad, > > can we try to reproduce this with a non-thread test program. If we can > > reproduce it this way, it will be much easier to debug. > > maybe using async socket i/o would reproduce it. > > threads implementations and debugging threads has improved from the bad > old days but I can understand the desire to avoid the issue. I actually like to find an easy way to reproduce it, because waiting for the luck of some scheduling is not funny. I need to understand when this issue happens before I can actually fix it. Regards Marcel _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel