Bug#296706: Bug#296708: libgphoto2-2: Segfaults after libusb upgrade
On Sat, Feb 26, 2005 at 03:29:53PM +0100, Aurélien Jarno wrote: > On Sat, Feb 26, 2005 at 02:52:26PM +0100, Milan Zamazal wrote: > > AJ> BTW, the original bug report mentions you are using a kernel > > AJ> 2.6.9. Are you still using the same kernel? > > > > Yes. (And don't forget libusb-0.1-4 1:0.1.8-17 still works perfectly.) > The way libusb communicate with the kernel with the kernel has changed > (thus your problem), and the problem appears only with the newest way. > BTW, the bug has just been fixed in 2.6.11-rc5-bk1. You seem to have gotten bug numbers crossed along the way; this bug is an RFA for the toshutils package. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Bug#296706: Bug#296708: libgphoto2-2: Segfaults after libusb upgrade
> "AJ" == Aurélien Jarno <[EMAIL PROTECTED]> writes: AJ> I have just produced two new test versions (test2 and test3), AJ> which should output some more debugging infos (that I hope AJ> useful). Could you please test them (no need to use a debug AJ> mode) and send me the output? test2: % gphoto2 --summary Transfer request on ep 4, 8 bytes length Submitting URB on ep 4, 8 bytes requested 8 bytes received / 8 bytes requested Transfer request on ep 131, 32774 bytes length Submitting URB on ep 131, 16384 bytes requested 10 bytes received / 16384 bytes requested Submitting URB on ep 131, 16384 bytes requested 0 bytes received / 16384 bytes requested zsh: segmentation fault gphoto2 --summary test3 (please note this one doesn't segfault and produces expected output): % gphoto2 --summary Transfer request on ep 4, 8 bytes length Submitting URB on ep 4, 8 bytes requested 8 bytes received / 8 bytes requested Transfer request on ep 131, 32774 bytes length Submitting URB on ep 131, 4096 bytes requested 10 bytes received / 4096 bytes requested Submitting URB on ep 131, 4096 bytes requested 0 bytes received / 4096 bytes requested Transfer request on ep 4, 1 bytes length Submitting URB on ep 4, 1 bytes requested 1 bytes received / 1 bytes requested Transfer request on ep 4, 9 bytes length Submitting URB on ep 4, 9 bytes requested 9 bytes received / 9 bytes requested Transfer request on ep 131, 32774 bytes length Submitting URB on ep 131, 4096 bytes requested 1 bytes received / 4096 bytes requested Submitting URB on ep 131, 4096 bytes requested 0 bytes received / 4096 bytes requested Transfer request on ep 4, 8 bytes length Submitting URB on ep 4, 8 bytes requested 8 bytes received / 8 bytes requested Transfer request on ep 131, 32774 bytes length Submitting URB on ep 131, 4096 bytes requested 10 bytes received / 4096 bytes requested Submitting URB on ep 131, 4096 bytes requested 0 bytes received / 4096 bytes requested Transfer request on ep 4, 1 bytes length Submitting URB on ep 4, 1 bytes requested 1 bytes received / 1 bytes requested Transfer request on ep 4, 12 bytes length Submitting URB on ep 4, 12 bytes requested 12 bytes received / 12 bytes requested Transfer request on ep 131, 32774 bytes length Submitting URB on ep 131, 4096 bytes requested 1 bytes received / 4096 bytes requested Submitting URB on ep 131, 4096 bytes requested 0 bytes received / 4096 bytes requested Transfer request on ep 4, 8 bytes length Submitting URB on ep 4, 8 bytes requested 8 bytes received / 8 bytes requested Transfer request on ep 131, 32774 bytes length Submitting URB on ep 131, 4096 bytes requested 12 bytes received / 4096 bytes requested Submitting URB on ep 131, 4096 bytes requested 0 bytes received / 4096 bytes requested Transfer request on ep 4, 1 bytes length Submitting URB on ep 4, 1 bytes requested 1 bytes received / 1 bytes requested Transfer request on ep 4, 12 bytes length Submitting URB on ep 4, 12 bytes requested 12 bytes received / 12 bytes requested Transfer request on ep 131, 32774 bytes length Submitting URB on ep 131, 4096 bytes requested 1 bytes received / 4096 bytes requested Submitting URB on ep 131, 4096 bytes requested 0 bytes received / 4096 bytes requested Transfer request on ep 4, 8 bytes length Submitting URB on ep 4, 8 bytes requested 8 bytes received / 8 bytes requested Transfer request on ep 131, 32774 bytes length Submitting URB on ep 131, 4096 bytes requested 31 bytes received / 4096 bytes requested Submitting URB on ep 131, 4096 bytes requested 0 bytes received / 4096 bytes requested Transfer request on ep 4, 1 bytes length Submitting URB on ep 4, 1 bytes requested 1 bytes received / 1 bytes requested Transfer request on ep 4, 12 bytes length Submitting URB on ep 4, 12 bytes requested 12 bytes received / 12 bytes requested Transfer request on ep 131, 32774 bytes length Submitting URB on ep 131, 4096 bytes requested 1 bytes received / 4096 bytes requested Submitting URB on ep 131, 4096 bytes requested 0 bytes received / 4096 bytes requested Transfer request on ep 4, 8 bytes length Submitting URB on ep 4, 8 bytes requested 8 bytes received / 8 bytes requested Transfer request on ep 131, 32774 bytes length Submitting URB on ep 131, 4096 bytes requested 29 bytes received / 4096 bytes requested Submitting URB on ep 131, 4096 bytes requested 0 bytes received / 4096 bytes requested Transfer request on ep 4, 1 bytes length Submitting URB on ep 4, 1 bytes requested 1 bytes received / 1 bytes requested Transfer request on ep 4, 12 bytes length Submitting URB on ep 4, 12 bytes requested 12 bytes received / 12 bytes requested Transfer request on ep 131, 32774 bytes length Submitting URB on ep 131, 4096 bytes requested 1 bytes received / 4096 bytes requested Submitting URB on ep 131, 40
Bug#296706: Bug#296708: libgphoto2-2: Segfaults after libusb upgrade
On Sat, Feb 26, 2005 at 02:52:26PM +0100, Milan Zamazal wrote: > AJ> BTW, the original bug report mentions you are using a kernel > AJ> 2.6.9. Are you still using the same kernel? > > Yes. (And don't forget libusb-0.1-4 1:0.1.8-17 still works perfectly.) The way libusb communicate with the kernel with the kernel has changed (thus your problem), and the problem appears only with the newest way. BTW, the bug has just been fixed in 2.6.11-rc5-bk1. I have just produced two new test versions (test2 and test3), which should output some more debugging infos (that I hope useful). Could you please test them (no need to use a debug mode) and send me the output? http://temp.aurel32.net/libusb/test/ Thanks, Aurelien -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#296706: Bug#296708: libgphoto2-2: Segfaults after libusb upgrade
> "AJ" == Aurélien Jarno <[EMAIL PROTECTED]> writes: AJ> Could you please send me the log of both libusb (the test AJ> version) and gphoto2 in debug mode? gphoto2 debug, strace gphoto2 and libusb debug logs are here: all-logs.bz2 Description: Binary data AJ> BTW, the original bug report mentions you are using a kernel AJ> 2.6.9. Are you still using the same kernel? Yes. (And don't forget libusb-0.1-4 1:0.1.8-17 still works perfectly.) AJ> And sorry to ask you a lot of thing, No problem, thank you for caring about the bug. Regards, Milan Zamazal -- Here is my advice, don't try to program the bleeding edge for the general populace unless you really, really, really like migraines. Neal H. Walfield
Bug#296706: Bug#296708: libgphoto2-2: Segfaults after libusb upgrade
On Sat, Feb 26, 2005 at 02:13:42PM +0100, Milan Zamazal wrote: > Unfortunately it still segfaults. Here is the log: That's strange, that doesn't seems to correspond to what gphoto2 says. Could you please send me the log of both libusb (the test version) and gphoto2 in debug mode? BTW, the original bug report mentions you are using a kernel 2.6.9. Are you still using the same kernel? Kernel version 2.6.11-rc1 and newer are buggy, and it is also the case of some series such as -ac, -mm, ... And sorry to ask you a lot of thing, I don't have the hardware to debug the problem. Bye, Aurelien -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#296706: Bug#296708: libgphoto2-2: Segfaults after libusb upgrade
> "AJ" == Aurélien Jarno <[EMAIL PROTECTED]> writes: AJ> Could you please test this version with USB_DEBUG=255 ? AJ> http://temp.aurel32.net/libusb/test/ Unfortunately it still segfaults. Here is the log: usb-test-log Description: Binary data Regards, Milan Zamazal -- If we are going to start removing packages because of the quality of the software, wonderful. I move to remove all traces of the travesty of editors, vi, from Debian, since obviously as editors they are less than alpha quality software. -- Manoj Srivastava in debian-devel
Bug#296706: Bug#296708: libgphoto2-2: Segfaults after libusb upgrade
Hi! After looking at the logs you send me and at the code, I may have found a problem. It seems to be possible that the kernel returns less data than expected, but returns some data. This is currently not handle in libusb. Could you please test this version with USB_DEBUG=255 ? http://temp.aurel32.net/libusb/test/ I hope this would fix your problem. Either it works or not, could you please send me the log? Bye, Aurelien -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#296706: Bug#296708: libgphoto2-2: Segfaults after libusb upgrade
> "AJ" == Aurélien Jarno <[EMAIL PROTECTED]> writes: AJ> Could you please try with USB_DEBUG=255 ? Here is the output: usb-log Description: Binary data Regards, Milan Zamazal -- When you're in a fight with an idiot, it's difficult for other people to tell which one the idiot is. -- Bruce Perens in debian-devel
Bug#296706: Bug#296708: libgphoto2-2: Segfaults after libusb upgrade
On Fri, Feb 25, 2005 at 07:34:49PM +0100, Milan Zamazal wrote: > > "AJ" == Aurélien Jarno <[EMAIL PROTECTED]> writes: > > AJ> Next step, could you please run gphoto2 in debugging mode to see > AJ> if there is something interesting in the output. For that, just > AJ> run gphoto2 --debug put_your_args_here > > Here's the output: 3.188609 sierra/library.c(2): Reading packet... 3.188661 gphoto2-port(2): Clear halt... 3.193595 gphoto2-port(2): Reading 32774=0x8006 bytes from port... 3.284674 gphoto2-port(2): Could only read 10 out of 32774 byte(s) That sounds strange 3.284731 gphoto2-port(3): Hexdump of 10 = 0xa bytes follows: 03 00 04 00 0a 00 00 00-0a 00.. 3.284751 gphoto2-port(2): Clear halt... 3.285657 sierra/library.c(2): Packet successfully read. 3.285697 sierra/library.c(2): Successfully read packet. Interpreting result (0x03) ^^ Actually the read is not successfull (10 of 32774 bytes) Ok, I think there is a bug somewhere in libusb, that makes it returning less data than asked. Then there is another bug in gphoto2. It should not interpret the data in that case. -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#296706: Bug#296708: libgphoto2-2: Segfaults after libusb upgrade
On Fri, Feb 25, 2005 at 06:22:11PM +0100, Aurélien Jarno wrote: > Milan Zamazal a écrit : > >AJ> Milan, could you please run USBDEBUG=255 gphoto2 > >AJ> put_your_args_here, and send me the result? > > > >This doesn't output anything. > Ok, I need to understand why. I given the wrong variable, sorry. Could you please try with USB_DEBUG=255 ? Thanks, Aurelien -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#296706: Bug#296708: libgphoto2-2: Segfaults after libusb upgrade
> "AJ" == Aurélien Jarno <[EMAIL PROTECTED]> writes: AJ> Next step, could you please run gphoto2 in debugging mode to see AJ> if there is something interesting in the output. For that, just AJ> run gphoto2 --debug put_your_args_here Here's the output: gphoto2-debug-log.bz2 Description: Binary data Regards, Milan Zamazal -- SomeProgrammersLikeWritingLikeThis.IDontThinkThisFormOfCommunicationIs\ AGoodIdea.IApologizeToAllWhoCantReadMyTextsWrittenInATraditionalStyle.
Bug#296706: Bug#296708: libgphoto2-2: Segfaults after libusb upgrade
Milan Zamazal a écrit : AJ> Milan, could you please run USBDEBUG=255 gphoto2 AJ> put_your_args_here, and send me the result? This doesn't output anything. Ok, I need to understand why. AJ> Also, doing an strace (just run strace gphoto2 AJ> put_your_args_here,) would be useful. I'll send it to you. I have looked at it, everything seems to be normal until the segfault. Next step, could you please run gphoto2 in debugging mode to see if there is something interesting in the output. For that, just run gphoto2 --debug put_your_args_here Thanks, Aurelien -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#296706: Bug#296708: libgphoto2-2: Segfaults after libusb upgrade
> "FP" == Frederic Peters <[EMAIL PROTECTED]> writes: FP> I rebuilt libgphoto2 against the new libusb; could you test the FP> packages from http://people.debian.org/~fpeters/libgphoto2/ ? No change, it still segfaults. > "AJ" == Aurélien Jarno <[EMAIL PROTECTED]> writes: AJ> Milan, could you please run USBDEBUG=255 gphoto2 AJ> put_your_args_here, and send me the result? This doesn't output anything. AJ> Also, doing an strace (just run strace gphoto2 AJ> put_your_args_here,) would be useful. I'll send it to you. Regards, Milan Zamazal -- http://www.zamazal.org
Bug#296706: Bug#296708: libgphoto2-2: Segfaults after libusb upgrade
Frederic Peters a écrit : Hi Aurelien Hi! Did the new libusb break ABI ? I can rebuild libgphoto2 against the new version but this won't fix other packages using libusb. No, the ABI is still the same. What has changed is the way to communicate with the kernel, the newer version allow bigger packets and increased transfer rate. What is your take on this ? I don't know what is the problem. libusb 0.1.9 is known to have problem with big transfers, but libusb 0.1.10 fixed the problem. Has somebody reported the same problem with an other backend? Milan, could you please run USBDEBUG=255 gphoto2 put_your_args_here, and send me the result? Also, doing an strace (just run strace gphoto2 put_your_args_here,) would be useful. Aurelien -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `-people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
