Re: libusb_init causes segfault

[Akos V. <ax...@gm...>]

I know, that my app is broken, and that is my bad, and I have already
corrected the error. Nonetheless nothing like that should cause a segfault.
Actually nothing should cause a segfault, not even improprer usage.
This is not embedded code, where a few bytes code length, or a few
microseconds execution time counts (especially at functions which are
called only a few times.)

Regards,
 Ákos Vandra


On 19 November 2012 13:43, Peter Stuge <pe...@st...> wrote:

> Akos Vandra wrote:
> > If libusb_init is supplied with a nil pointer, it causes a segfault. Even
> > though this is a user application error, it should be checked, and an
> error
> > should be returned.
>
> libusb on purpose doesn't check application data, and adding checks
> would need to be not just in libusb_init but in every function for
> every parameter. That was never really desirable, even during design
> discussion for the 1.0 API many years ago.
>
> Documentation patches to make it more clear what parameters are
> allowed where are of course always welcome!
>
>
> Thanks
>
> //Peter
>
>
> ------------------------------------------------------------------------------
> Monitor your physical, virtual and cloud infrastructure from a single
> web console. Get in-depth insight into apps, servers, databases, vmware,
> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
> Pricing starts from $795 for 25 servers or applications!
> http://p.sf.net/sfu/zoho_dev2dev_nov
> _______________________________________________
> libusb-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-devel
>