Re: error code from afb

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Jose

Thank you for your response and your work for documentation.
We are looking forward to get info from that documentation.

Thanks/BR
ChenWei
-----Original Message-----
From: José Bollo [mailto:jose.bollo@xxxxxxx] 
Sent: Friday, September 7, 2018 4:30 PM
To: I37546 Chin I
Cc: fulup.arfoll@xxxxxxx; loic.collignon@xxxxxxx; automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx; I25461 Momiyama Yoshito
Subject: Re:  error code from afb

On Thu, 6 Sep 2018 05:31:19 +0000
<I37546_CHIN@xxxxxxxxxxxxxx> wrote:

> Hi Jose
> 
> Sorry for some misleading.
> Although errors come to bindings are also useful to us, currently
> we'd like to know the ones come to APPs.
> 
> We understand that they mostly come from binding's reply,
> But we think there are still ones come from afb itself or from base
> system since it uses IPC.
> 
> 1. error from afb_ws_client_connect_api, afb_wsj1_call_s(when use wsj
> lib) 2. signals/errno from system

Hi ChenWei,

Sorry for the late answer.

I created https://jira.automotivelinux.org/browse/SPEC-1727 to track
that improvement job. I plan to work on it next week.

Best regards
José

> are maybe considerable to us.
> 
> A documentation will help us and the other APPs well if it's not
> difficult to do.
> 
> Thanks/BR
> ChenWei
> -----Original Message-----
> From: José Bollo [mailto:jose.bollo@xxxxxxx] 
> Sent: Wednesday, September 5, 2018 9:00 PM
> To: I37546 Chin I
> Cc: josé bollo; Fulup Ar Foll; Loïc Collignon [ IoT.bzh ];
> automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx; I25461 Momiyama
> Yoshito Subject: Re:  error code from afb
> 
> 2018-09-05 13:18 GMT+02:00  <I37546_CHIN@xxxxxxxxxxxxxx>:
> > Hi Jose
> >
> > We'd like to know all kinds error code come from afb to APPs,
> > but we can't find the error define in afb headers
> >
> > Do we have an error define table? Or all the error codes are set
> > into errno?  
> 
> Hi ChenWei,
> 
> All errors are reported using errno and a meaningful code picked in
> "man errno" list.
> 
> Currently the error code used are: E2BIG, EAFNOSUPPORT, EBADMSG,EBUSY,
> ECONNABORTED, EEXIST, EFAULT, EFBIG, EINTR, EINVAL, ENAMETOOLONG,
> ENOENT, ENOMEM, ENOTDIR, EPERM, EPIPE. Advantage of using system
> predefined codes is the availability of strerror (and %m) and its
> translations.
> 
> Not all of these codes are returned to bindings. Conversely, some
> error reported by the system are returned directly (Think about
> afb_api_rootdir_open_locale [1] that calls 'open'). Telling exactly
> what error can be reported by what function shouldn't be so difficult.
> It is probably a valuable documentation to add. Should we open a JIRA
> issue to track that work?
> 
> This is for what bindings receive. About applications, it is different
> because they receive errors from bindings, not from binder.
> 
> Best regards
> José Bollo
> 
> [1]
> https://docs.automotivelinux.org/docs/apis_services/en/dev/reference/af-binder/reference-v3/func-api.html#afbapirootdiropenlocale
> 
> > Thanks/BR
> > ChenWei  

_______________________________________________
automotive-discussions mailing list
automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions




[Index of Archives]     [LARTC]     [Bugtraq]     [Yosemite Forum]     [Photo]

  Powered by Linux