From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] hcid crashes with "buffer overflow detected" when pairing
Date: Tue, 20 Sep 2005 13:43:50 +0200 [thread overview]
Message-ID: <1127216630.5168.22.camel@localhost.localdomain> (raw)
In-Reply-To: <1126981781.14893.27.camel@yeti>
Hi Fredrik,
> I'm trying out the following packages on Fedora Core 4, x86_64:
>
> bluez-pin-0.24-2
> bluez-libs-2.20-1
> bluez-utils-2.20-1
> dbus-0.33-3
>
> Unfortunately hcid crashes with "buffer overflow detected" when pairing.
> Is this a known problem?
try bluez-utils-2.21 or the latest CVS. I fixed some possible buffer
overflows lately.
> Marcel, I'm happy you decided on moving to ASCII based storage. Is there
> any documentation on this? Perhaps I can update the man pages if I can
> get this working.
I did this some time ago and no, it is not documented at the moment.
Feel free to update all the manual pages. The hidd also now caches the
device information.
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-09-20 11:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-17 18:29 [Bluez-devel] hcid crashes with "buffer overflow detected" when pairing Fredrik Noring
2005-09-19 11:35 ` Claudio Takahasi
2005-09-20 11:43 ` Marcel Holtmann [this message]
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=1127216630.5168.22.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox