From: Florian Ragwitz <rafl@debian.org>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] hcidump segfault
Date: Mon, 19 Feb 2007 10:51:45 +0100 [thread overview]
Message-ID: <20070219095145.GA1828@perldition.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 729 bytes --]
Hello,
I'm trying to sync a Sony Ericsson W810i mobile using wammu over
bluetooth. Scanning for the device works fine, but when trying to
connect wammu hangs. I tried to debug that problem using hcidump and
saw it segfaulting after telling wammu to connect. Therefor I think the
problem is caused by something other than the wammu/gammu code or my
local bluetooth configuration.
Maybe someone can help me sort out the above problems? [1]Here you will
find the hcidump output of a wammu session which first scans for the
device and then tries to connect to it. What other information might be
useful?
1. http://files.perldition.org/wammu.hcidump
TIA,
Flo
--
BOFH excuse #25:
Decreasing electron flux
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 345 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2007-02-19 9:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 9:51 Florian Ragwitz [this message]
2007-02-19 10:18 ` [Bluez-users] hcidump segfault 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=20070219095145.GA1828@perldition.org \
--to=rafl@debian.org \
--cc=bluez-users@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