[fpc-pascal] USB Human Interface Devices
Stefan V. Pantazi
svpantazi at gmail.com
Sat Aug 17 22:11:21 CEST 2019
Is the segfault in the same place or has it changed?
To debug further, you have to compare sizes of data structures, field
types and function call parameter types between the libusb 1.0 and the
old libusb0.1. - any mismatch could result in a segfault.
On 8/17/19 3:51 PM, James Richters wrote:
> Oops, I got mixed up.. it's usb.pas that isn't used anymore... I changed LibUsb to stdcall and not it compiles again.. but I still get he access violation with stdcall.
>
> James
>
>
>> from the copy of your github, looks like libusboop.pas has a uses statement for libusb.pas; so libusb.pas is still used
>
>> https://github.com/Zaaphod/pas-libusb/blob/Hack/src/libusboop.pas (line 30)
>
>> Uses
>> Classes, SysUtils, LibUsb;
>
> _______________________________________________
> fpc-pascal maillist - fpc-pascal at lists.freepascal.org
> https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
>
--
_______________________________________________________
More information about the fpc-pascal
mailing list