Pete Batard wrote:
> I have now pushed a patch that adds libusb0.sys and libusbK.sys
> support there, for testing.
I look forward to some testing! Even if it comes at the cost of the
libusbK DLL it's still very nice that libusb-1.0 code can be used
with the libusb-win32 driver.
> To fetch the br
All,
If you have some interest with regards to libusb-win32 and libusbK
driver support, you may want to have a look at the new 0K ("zero K")
branch from the pbatard/libusbx repo on github [1].
I have now pushed a patch that adds libusb0.sys and libusbK.sys support
there, for testing.
To fetch
Pete Batard wrote:
> Of course it would be quite ironic if intel were the ones who pushed MS
> and others to use ia64 in the first place, in order to push brand
> recognition (ia = "Intel Architecture"), and got bitten at their own
> game when their competitor both followed suit with amd64 and a
On 2012.08.07 14:47, sebasti...@gmx-topmail.de wrote:
> Just for information:
> I got another core dump with the libusbx compiled on monday.
> Are you interested in this one?
It breaks at the same location, so it will provide the same information
as what we already know.
Just to confirm, you may
Just for information:
I got another core dump with the libusbx compiled on monday.
Are you interested in this one?
Program terminated with signal 11, Segmentation fault.
#0 0x00115e89 in add_to_flying_list (transfer=0xb5600468) at io.c:1175
1175io.c: Datei oder Verzeichnis nicht gefunden.
On 2012.08.07 13:00, sebasti...@gmx-topmail.de wrote:
>> On 2012.08.07 12:44, Pete Batard wrote:
>> Did you get the impression that crash happened sooner than the previous
>> ones this time around, or what is about the same?
> Very hard to say. To me it seems that the failure occurs totally
> rando
> On 2012.08.07 12:44, Pete Batard wrote:
> Did you get the impression that crash happened sooner than the previous
> ones this time around, or what is about the same?
Very hard to say. To me it seems that the failure occurs totally
randomly. Sometimes after some hours, sometimes after several day
On 2012.08.07 08:30, sebasti...@gmx-topmail.de wrote:
Please see the attached file with a new backtrace of the segmentation
fault. The file contains all of the commands you told me to execute
last week.
Thanks for the report.
Did you get the impression that crash happened sooner than the previ
Good morning Pete, Ludovic and Orin,
yesterday, I recompiled the latest libusbx version from the git
repository with debug information (version 1.0.12.10545) and replaced
it on the computers.
> On 2012.08.03 15:51, Pete Batard wrote:
> If you do observe the crash again, and since you're recompil
