On 21/02/13 00:30, Pete Batard wrote:
> While fixing #69 [1] (which has now been pushed), I got bothered by an 
> assertion error that was due to closing stdout, and since I didn't 
> initially get what the stdout redirection was all about here, I 
> decided to (hopefully) simplify it.

I didn't realise that Windows didn't like you closing standard out, I 
guess I never tried a debug build after adding the stdout redirection.

> The attached patch is the result of that.
> It also switches the context test to using INFO rather then DEBUG, as 
> a lot of polluting info is generated in verbose mode otherwise, and I 
> don't think this impacts the test.

I used DEBUG to start with as that's how I'd seen the issue that I was 
trying to reproduce in the test. With it set to INFO I don't see 
anything getting output in this tests. I think this means it would no 
longer expose the issue that this test discovered that was fixed in:
https://github.com/libusbx/libusbx/commit/ce75e9af3f9242ec328b0dc2336b69ff24287a3c

>
> Note that I haven't tested this patch on WinCE, or any other platform 
> but Windows for that matter.

Builds fine on WinCE for me.

Regards,

Toby

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel

Reply via email to