Eekle

> @Eekle Can you please also try this PR, with your device from #1039? Could you give me a minimal example I can build to test this? My original bug...

I have tested v1.0.25 of libusb and this PR, by building and running `xusb.exe VID:PID` (with the VID and PID of the offending device. v1.0.25 produces a read access violation....

Current master produces the same output: ``` Reading first configuration descriptor: total length: 135 descriptor length: 9 nb interfaces: 3 interface[0]: id = 0 interface[0].altsetting[0]: num endpoints = 0 Class.SubClass.Protocol:...

@tepozoa Would be a good issue for a separate PR I think - style the ToC differently on Mobile so it appears above, rather than next to, the wiki.

@lafriks that would be the ideal UX. But I was trying to avoid a js solution because I'm not sure how to implement it in this codebase.

That seems to have fixed it.

I don't understand what you mean sorry. Imagine I had some module to test like... ``` // module.h extern int[NUM_ELEMENTS] my_array; bool add_to_array(int element); // module.c int[NUM_ELEMENTS] my_array; bool add_to_array(int...

What I mean is that the number of elements in the array is controlled by a `#define`. So we might want to test that changing the value of the `#define`...

That's fine if the flag can be subbed out for a `const int` like that. I usually deal with that situation by just linking a different definition of `bla` in...

I'm using a define'd length array because it's a simple example of what I'm talking about, rather than it being specifically what I need to do. This actually came up...