Skip to content
This repository has been archived by the owner on May 4, 2021. It is now read-only.

Image causing segmentation fault #144

Open
Joelgranados opened this issue Nov 30, 2014 · 7 comments
Open

Image causing segmentation fault #144

Joelgranados opened this issue Nov 30, 2014 · 7 comments

Comments

@Joelgranados
Copy link
Contributor

This image causes segmentation fault
bvz0036-gc02l-c01 fullres-orig_2014_06_03_08_00_00_00

@Joelgranados
Copy link
Contributor Author

The image is corrupted in some way, and should just be ignored. Instead it causes a seg fault. Not sure where and not sure in what component.

@kdm9
Copy link
Member

kdm9 commented Nov 30, 2014

Try running:

import skimage.io
skimage.io.imread("image", plugin="freeimage")

If that segfaults, then it's the bug I found a while ago. If so, pip
install from scikit image's master git branch.

Cheers,
K

On Sun, Nov 30, 2014 at 11:34:56AM -0800, Joel Andres Granados wrote:

The image is corrupted in some way, and should just be ignored. Instead it causes a seg fault. Not sure where and not sure in what component.


Reply to this email directly or view it on GitHub:
#144 (comment)

@Joelgranados
Copy link
Contributor Author

I just did a pip install git+https://github.com/scikit-image/scikit-image.git@master and the segmentation fault still persisists. Can you confirm that you fix addesses this issue? What happens when you run skimage.io.imread("image", plugin="freeimage") Notice that I made sure that your e63ae9450ac7b236e5dcbf859d8fc7f8741bf304 in skimage was present in my install.

@kdm9
Copy link
Member

kdm9 commented Dec 1, 2014

OK, that's a new bug then. Will investigate tomorrow, but my fix to skimage definitely fixed the old bug.

@kdm9
Copy link
Member

kdm9 commented Dec 1, 2014

Where is that image on phenocam?

@kdm9
Copy link
Member

kdm9 commented Dec 1, 2014

Also, can you send a gdb backtrace? Thanks

(P.S., remember to wrap the backtrace in triple backquotes if you paste it in here, or it will reference all issues, as the stack level indicator lines start with # followed by the backtrace depth.)

Cheers,
K

@Joelgranados
Copy link
Contributor Author

Image is the one I uploaded to this bug. The way to reproduce it is the three line code snipped that you posted previously. Here goes the backtrace:

#0  0x00007ffff34c8949 in ffi_closure_unix64_inner () from /usr/lib/x86_64-linux-gnu/libffi.so.6
#1  0x00007ffff34c8e64 in ffi_closure_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
#2  0x00007fffebc43f7e in FreeImage_OutputMessageProc () from /usr/lib/libfreeimage.so.3
#3  0x00007fffebc563f3 in ?? () from /usr/lib/libfreeimage.so.3
#4  0x00007ffff1db97f5 in ?? () from /usr/lib/x86_64-linux-gnu/libjpeg.so.8
#5  0x00007fffebc565b9 in ?? () from /usr/lib/libfreeimage.so.3
#6  0x00007ffff1db159e in ?? () from /usr/lib/x86_64-linux-gnu/libjpeg.so.8
#7  0x00007ffff1db2dbf in ?? () from /usr/lib/x86_64-linux-gnu/libjpeg.so.8
#8  0x00007ffff1daf935 in ?? () from /usr/lib/x86_64-linux-gnu/libjpeg.so.8
#9  0x00007ffff1db4b9e in ?? () from /usr/lib/x86_64-linux-gnu/libjpeg.so.8
#10 0x00007ffff1dad3da in jpeg_read_scanlines () from /usr/lib/x86_64-linux-gnu/libjpeg.so.8
#11 0x00007fffebc56f38 in ?? () from /usr/lib/libfreeimage.so.3
#12 0x00007fffebc46914 in FreeImage_LoadFromHandle () from /usr/lib/libfreeimage.so.3
#13 0x00007fffebc469b1 in FreeImage_Load () from /usr/lib/libfreeimage.so.3
#14 0x00007ffff34c8cfc in ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
#15 0x00007ffff34c862c in ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
#16 0x00007ffff36d7df5 in _ctypes_callproc () from /home/joel/.virtualenvs/timestreamlib/lib/python2.7/lib-dynload/_ctypes.x86_64-linux-gnu.so
#17 0x00007ffff36dc642 in ?? () from /home/joel/.virtualenvs/timestreamlib/lib/python2.7/lib-dynload/_ctypes.x86_64-linux-gnu.so
#18 0x00000000004c3cab in PyEval_EvalFrameEx ()
#19 0x00000000004c3762 in PyEval_EvalFrameEx ()
#20 0x00000000004c1859 in PyEval_EvalCodeEx ()
#21 0x00000000004c34aa in PyEval_EvalFrameEx ()
#22 0x00000000004dd940 in ?? ()
#23 0x00000000004c68d8 in PyEval_EvalFrameEx ()
#24 0x00000000004dd940 in ?? ()
#25 0x00000000004c68d8 in PyEval_EvalFrameEx ()
#26 0x00000000004c1859 in PyEval_EvalCodeEx ()
#27 0x00000000004c34aa in PyEval_EvalFrameEx ()
#28 0x00000000004c1859 in PyEval_EvalCodeEx ()
#29 0x00000000004fa7ff in ?? ()
#30 0x00000000004480f8 in PyRun_InteractiveOneFlags ()
#31 0x0000000000447e9e in PyRun_InteractiveLoopFlags ()
#32 0x000000000042cdc1 in ?? ()
#33 0x0000000000492243 in Py_Main ()
#34 0x00007ffff6f15b45 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
#35 0x0000000000491c25 in _start ()

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants