[Motmot] Segmentation faults
John Schneider
jzschneider at gmail.com
Thu Mar 26 22:29:53 UTC 2009
I get the same output from the backtrace for all three computers:
...
(no debugging symbols found)
[New Thread 0xaf6b8b90 (LWP 9591)]
[New Thread 0xaeeb7b90 (LWP 9592)]
(no debugging symbols found)
[New Thread 0xae656b90 (LWP 9593)]
(no debugging symbols found)
[New Thread 0xade55b90 (LWP 9594)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xae656b90 (LWP 9593)]
0x00000000 in ?? ()
(gdb) bt
#0 0x00000000 in ?? ()
#1 0xaf78860c in raw1394_loop_iterate () from /usr/lib/libraw1394.so.8
#2 0xaf789348 in raw1394_write () from /usr/lib/libraw1394.so.8
#3 0xaf7a7ff7 in platform_camera_write () from /usr/lib/libdc1394.so.22
#4 0xaf79bdb9 in dc1394_set_control_registers () from /usr/lib/libdc1394.so.22
#5 0xaf79727e in dc1394_video_set_transmission ()
from /usr/lib/libdc1394.so.22
#6 0xaf930856 in CCdc1394_close () from /usr/lib/libcam_iface_dc1394.so
#7 0xaf931522 in delete_CCdc1394 () from /usr/lib/libcam_iface_dc1394.so
#8 0xb7bbe0b1 in delete_CamContext () from /usr/lib/libcam_iface_unity.so
#9 0xb5869833 in ffi_call_SYSV ()
from /usr/lib/python2.5/lib-dynload/_ctypes.so
#10 0xb586966a in ffi_call () from /usr/lib/python2.5/lib-dynload/_ctypes.so
#11 0xb5864534 in _CallProc () from /usr/lib/python2.5/lib-dynload/_ctypes.so
#12 0xb585e02a in ?? () from /usr/lib/python2.5/lib-dynload/_ctypes.so
#13 0x0805cb97 in PyObject_Call ()
#14 0x080c7aa7 in PyEval_EvalFrameEx ()
#15 0x080c96e5 in PyEval_EvalFrameEx ()
#16 0x080cb1f7 in PyEval_EvalCodeEx ()
#17 0x081136b6 in ?? ()
#18 0x0805cb97 in PyObject_Call ()
#19 0x080c7e04 in PyEval_EvalFrameEx ()
#20 0x080c96e5 in PyEval_EvalFrameEx ()
---Type <return> to continue, or q <return> to quit---
#21 0x080c96e5 in PyEval_EvalFrameEx ()
#22 0x080cb1f7 in PyEval_EvalCodeEx ()
#23 0x0811372e in ?? ()
#24 0x0805cb97 in PyObject_Call ()
#25 0x08062bfb in ?? ()
#26 0x0805cb97 in PyObject_Call ()
#27 0x080c2e9c in PyEval_CallObjectWithKeywords ()
#28 0x080f59a8 in ?? ()
#29 0xb7f304fb in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#30 0xb7e84e5e in clone () from /lib/tls/i686/cmov/libc.so.6
On Thu, Mar 26, 2009 at 4:59 PM, Andrew Straw <astraw at caltech.edu> wrote:
> Andrew Straw wrote:
>> That being said, it's possible this bug has been fixed.
>>
> To be clear: it's possible more recent versions of Ubuntu will have
> fixed this particular bug, even though the present 1394 infrastructure
> is not going to continue for much longer.
> _______________________________________________
> Motmot mailing list
> Motmot at code.astraw.com
> http://code.astraw.com/cgi-bin/mailman/listinfo/motmot
>
More information about the Motmot
mailing list