Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 95909 - libgphoto2 make gphoto2 segfault
Summary: libgphoto2 make gphoto2 segfault
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: High critical (vote)
Assignee: Alastair Tse (RETIRED)
URL: http://bugs.debian.org/cgi-bin/bugrep...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-12 16:04 UTC by Dan Andresan
Modified: 2005-06-24 08:19 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Andresan 2005-06-12 16:04:37 UTC
please bare with me and read below: 
i emerged the new libusb 0.1.10a marked stable on 7th of June. 
reemerged libgphoto2 and gphoto2 to use the new libusb. 
everytime I try to get the pictures from my camera with gphoto2 -P 
I get Segmentation fault. 
Identified the exact bug in Debian's bug list, explained and fixed. What's 
happening is the following: 
AJ>I have looked at the libgphoto2 
AJ> sources, and there is something really strange. All buffers are 
AJ> 4096 bytes long whereas the requested data size is 32778 bytes. 
 
AJ> This was not a problem with the previous implementation of 
AJ> libusb as it seems that the camera always return smaller 
AJ> packets. With the new implementation, the kernel starts by 
AJ> clearing the data buffer believing it is 32778 bytes long, 
AJ> probably resulting in clearing local variables, and thus causing 
AJ> the segfault. 
 
Full details at the website indicated above. 
so there is a bug in libgphoto2 which makes gphoto2 crash with the new libusb. 
 
suggested fix: patch to change the size of buffers in libgphoto2 (as Debian 
did). 

Reproducible: Always
Steps to Reproduce:
 
 



Thank you.
Comment 1 Alastair Tse (RETIRED) gentoo-dev 2005-06-24 08:19:54 UTC
i believe this is fixed in the newly committed 2.1.6. thanks for your report.