> On Mon, Jul 4, 2016 at 4:24 PM, Julien Delplanque <jul...@tamere.eu> wrote: >> Hello again Esteban, all others, >> >> I am still experiencing strange behaviors with the objects in the external >> array. >> >> I get a lot of NULL pointers and some strange addresses (I guess, I am not a >> C expert) that are close to NULL >> (see the screenshot attached). These objects make the VM crash (segmentation >> fault) when I call a function >> from the libusb binding (for NULL objects it may be ok but what about >> others?). Some other objects (those with >> a normal address in the screenshot) work finely with the functions calls >> using UFFI... >> >> This kind of bug is not reported in libusb discussions I found on the >> internet and I tried an example in C, >> there is no NULL pointer received from the function (they are not even >> considered in official examples). >> >> So I guess the problem may come from Pharo? >> >> Do you have any idea of what it could be? >> >> I will be available on Slack all the day if you want. :) >> >> Thanks in advance, >> >> Julien
On Mon, Jul 4, 2016 at 6:15 PM, Ben Coman <b...@openinworld.com> wrote: > How does it compare with the result you get in pure C? > e.g. using this code... > http://libusb.org/browser/libusb/examples/lsusb.c?rev=efc29733ad31f81883a7ac51a6cc6cda9ad4feb9&order=name > Also, what is the return value of calling libusb_init() from Pharo? cheers -ben
