From: Marcel Holtmann <marcel@holtmann.org>
To: Xavier Garreau <xavier@xgarreau.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Wrong errno
Date: 29 Oct 2003 16:38:25 +0100 [thread overview]
Message-ID: <1067441911.24041.284.camel@pegasus> (raw)
In-Reply-To: <200310281437.01092.xavier@xgarreau.org>
Hi Xavier,
> I'm currently developping an application with bluez. I wrote a little code to
> test the alarm behaviour with bluez sockets code.
>
> The connect and read (or recv) get interrupted but errno is set to ESPIPE (29)
> instead of EINTR (4). Does any one of you guys know why i'm getting this
> illegal seek operation errno ?
I don't see any usage of ESPIPE in L2CAP, so this can be a general
behaviour of the socket code. What errno do you get if you try this with
TCP socket code?
BTW what kernel and/or patches do you use?
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2003-10-29 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-28 13:37 [Bluez-devel] Wrong errno Xavier Garreau
2003-10-28 19:11 ` Aurelien Minet
2003-10-29 8:48 ` Xavier Garreau
2003-10-29 15:38 ` 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=1067441911.24041.284.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=xavier@xgarreau.org \
/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