Closed JanKalin closed 2 years ago
there is memory corruption in the log, so there is some bug. I will try to reproduce with one of my cameras here
We have been noticing this issue randomly with C++ libraries, that are built on gphoto2 2.5.26.1
, on Canon EOS 800D
cameras.
@msmeissn Is this fixed in the newer version. If not, please let us know the workarounds.
The S45 is using the very old canon driver.
Canon EOS 800D uses the ptp2 driver, there i have so far no reports of crashes. can you get gdb backtraces or valgrind output?
Sorry i dropped the ball on the research on the S45 above, need to pick it up.
Unfortunately, I don't have this reports or the core-dump. I'll try to fetch it. Is there any way I can get this after a segfault has occurred.
the (old canon) directory compare functiuon was not using bounds checks, but relied on some condition which we could not guarantee
I added size checks now, please check if it helps.
A year and a bit later (having not had the need for gphoto2 before)
Yes, gphoto2 v2.5.28.1 with libgphoto2 v2.5.30.1 work well, without segfaults, I cannot reproduce the error any more.
Describe the bug
When using option
--capture-image-and-download
the program segfaults when attempting to delete the file on camera. Afterwards the camera must be turned of and on again to start working with gphoto again.Name the camera
libgphoto2 and gphoto2 version Running on Raspbian Raspberry Pi 4
To Reproduce
The two log files are attached. before_segfault.txt after_segfault.txt
Apparently the problem occurs only when the photo is not the last one: