From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Strange behaviour
Date: Thu, 01 Jun 2006 17:01:09 -0600 [thread overview]
Message-ID: <447F71B5.8060905@xmission.com> (raw)
In-Reply-To: <1149202516.32406.0.camel@localhost>
Marcel
> 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.
brad
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-06-01 23:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 17:01 [Bluez-devel] Strange behaviour Brand, Chris
2006-06-01 17:56 ` Marcel Holtmann
2006-06-01 21:11 ` Marcel Holtmann
2006-06-01 21:16 ` Brand, Chris
2006-06-01 22:55 ` Marcel Holtmann
2006-06-01 23:01 ` Brad Midgley [this message]
2006-06-01 23:11 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2006-05-17 17:51 Brand, Chris
2006-05-29 13:22 ` Marcel Holtmann
2006-05-29 16:13 ` Brand, Chris
2006-05-29 17:36 ` Marcel Holtmann
2006-05-29 17:57 ` Brand, Chris
2006-05-29 18:44 ` Marcel Holtmann
2006-05-29 18:48 ` Brand, Chris
2006-05-29 19:00 ` Marcel Holtmann
2006-05-29 19:01 ` Brand, Chris
2006-05-29 20:21 ` Marcel Holtmann
2006-05-29 20:33 ` Brand, Chris
2006-05-29 20:37 ` Marcel Holtmann
2006-05-29 20:39 ` Brand, Chris
2006-05-31 18:08 ` Brand, Chris
2006-05-31 20:08 ` Marcel Holtmann
2006-06-01 16:55 ` Brand, Chris
2006-06-01 17:54 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=447F71B5.8060905@xmission.com \
--to=bmidgley@xmission.com \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.