-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
binwalk/git segfault #30
Comments
Interesting; based on the output it looks like libmagic is segfaulting during its initialization. What version of libmagic do you have installed on your system? Also, how did you install binwalk, as it seems that not all components were installed properly (namely libcompress42 and libtinfl seem to be missing)? |
Any word on this? I have not been able to reproduce this on either 32 or 64 bit systems. |
Was able to reproduce the issue on a Mac; this was caused by improper handling of the magic_open return value in binwalk's ctypes wrapper (though it seems to work on some systems). The code in the master branch has been patched appropriately. |
[I] sys-apps/file (5.17@26.02.2014)
[I] dev-lang/python (2.7.6(2.7)@04.12.2013)
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff5867057 in ?? () from /usr/lib64/libmagic.so.1
(gdb) bt
#0 0x00007ffff5867057 in ?? () from /usr/lib64/libmagic.so.1
#1 0x00007ffff5861143 in ?? () from /usr/lib64/libmagic.so.1
#2 0x00007ffff7e1b6e4 in ffi_call_unix64 () from /usr/lib64/libffi.so.6
#3 0x000000000000000a in ?? ()
#4 0x00007fffffff9c60 in ?? ()
#5 0x00007fffffff9bf0 in ?? ()
#6 0x00007ffff7e1b275 in ffi_call () from /usr/lib64/libffi.so.6
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
The text was updated successfully, but these errors were encountered: