On 2012.11.13 10:23, Toby Gray wrote: > I've been tempted to write a simple test application to do things > similar to this for a while now. Just a few for loops which call various > APIs many hundreds of times to help detect memory leaks.
That would be nice. I see no issue adding such a test app to our samples. > The only thing > which has really stopped me is that I couldn't decide if it should be an > example (so live in examples/stress_test.c) or to create a new test > directory for test source. I'd say for now, if it's only one test app, examples will be just fine. But location doesn't matter vs content: we can always move it around at a later date if we feel like it. > Are you thinking of this[1] change? > > [1] - > https://github.com/libusbx/libusbx/commit/e82c677b5f10a966c89f6b58caa1ae4341260527 THANK YOU!!! I'm starting to think I overlooked something when I tried to improve on your patch, which may explain this new issue... Regards, /Pete ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
