From: Carl K <carl@personnelware.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] seg fault in rfcomm
Date: Fri, 09 Jun 2006 05:22:15 -0500 [thread overview]
Message-ID: <44894BD7.6030705@personnelware.com> (raw)
In-Reply-To: <1149847968.6618.73.camel@localhost>
Marcel Holtmann wrote:
> Hi Carl,
>
>
>> carl@asus17:~$ sudo hcitool scan
>> Scanning ...
>> 08:00:37:03:EF:36 PM325 by LG
>> carl@asus17:~$ sudo rfcomm connect 0 08:00:37:03:EF:36 4
>> Connected /dev/rfcomm0 to 08:00:37:03:EF:36 on channel 4
>> Press CTRL-C for hangup
>>
>> Segmentation fault
>>
>
> this shouldn't happen. What version is this and what platform you are
> running this on. Try the latest version from CVS and run it with gdb to
> get the backtrace.
>
>
RFCOMM configuration utility ver 2.24
carl@asus17:~$ uname -a
Linux asus17 2.6.15-23-686 #1 SMP PREEMPT Tue May 23 14:03:07 UTC 2006
i686 GNU/Linux
First i need to figure out how to do it again.
C
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2006-06-09 10:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 10:00 [Bluez-users] seg fault in rfcomm Carl K
2006-06-09 10:12 ` Marcel Holtmann
2006-06-09 10:22 ` Carl K [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=44894BD7.6030705@personnelware.com \
--to=carl@personnelware.com \
--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 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.