On 2012.05.26 12:16, Xiaofan Chen wrote: >> Hmm, it does seem to work. "xusb -d" is probably different >> and strangely it does not seem to honor the LIBUSB_DEBUG environment >> variable.
Note that the -d option of xusb came from toggleable logging, since it relies on set_debug which of course won't do much for debug logging unless it was already enabled. Until we have toggleable logging, I'm not going to pay much attention to aspects of -d not working in xusb. > Hmm, it does seem to honor the environment variable. > > The only thing is that I was confused by Pete's statement that "It only > displays the timestamp and thread ID if the global logging level > has been set to debug". Global logging level can be the one you set with an env variable or the one you set with libusb_set_debug (which should really have been called libusb_set_log_level as its intent may be confusing). > I think that statement is not totally correct. In the case of > "xusb -d" example, the error message will have the timestamp > no matter the logging level setting. Expected since timestamps are displayed if debug is enabled and -d sets the displaying of debug messages. Again, don't think there's much point looking at -d of xusb before we have toggleable logging. Regards, /Pete ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
