Opened 5 years ago
Last modified 5 years ago
#30 assigned enhancement
exit with error code when a transfer fails
| Reported by: | zany | Owned by: | zany |
|---|---|---|---|
| Priority: | blocker | Milestone: | |
| Component: | obexftp | Version: | |
| Keywords: | Cc: | manuel@… |
Description
From sf user summetj: ObexFTP fails with an exit code of 1 if it is not able
to find a specified bluetooth client.
However, if it DOES find the client, and starts a transfer, but the (put)
transfer is interrupted half way through, it returns with a success code
(0) instead of an error code (1 or something other than 0).
Attachments (1)
Change History (3)
Changed 5 years ago by manuelnaranjo
comment:1 Changed 5 years ago by manuelnaranjo
- Cc manuel@… added
- Priority changed from minor to blocker
- Type changed from defect to enhancement
This patch I just added (errno.patch) adds real support for errno.
Commit #223 added some support for errno and exit but was missing some parts, this patch adds a real non zero retval when something weird has happened. And it's using errno as retval instead of the function retval which doesn't mean anything in most cases.
For questions please contact me on mail
comment:2 Changed 5 years ago by zany
- Owner changed from somebody to zany
- Status changed from new to assigned
Looks good. Thanks Manuel!
The whole error code hiding in OpenOBEX needs some love still. I'll get to that someday too ;)
Add real support for errno