Hide Forgot
abrt version: 1.1.14 architecture: i686 cmdline: xiphos comment: I do not know if this is reproducable a I have installed all of the modules I currently need. component: xiphos crash_function: pthread_cond_timedwait@@GLIBC_2.3.2 executable: /usr/bin/xiphos kernel: 2.6.35.10-74.fc14.i686 package: xiphos-3.1.4-1.fc14 rating: 4 reason: Process /usr/bin/xiphos was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1296518870 uid: 500 backtrace ----- [New Thread 2388] [New Thread 2389] [New Thread 2390] [New Thread 2391] [New Thread 2392] [New Thread 2393] [New Thread 2394] [New Thread 2447] [New Thread 2448] [New Thread 2449] Core was generated by `xiphos'. Program terminated with signal 11, Segmentation fault. #0 0x080a19b1 in BackEnd::get_entry_attribute (this=0xa93c660, level1=0x80e0d6b "Heading", level2=0x80e0d62 "Preverse", level3=0xbf808db4 "0") at ../src/backend/sword_main.cc:655 655 ../src/backend/sword_main.cc: No such file or directory. in ../src/backend/sword_main.cc Thread 10 (Thread 2449): #0 0x001d0416 in __kernel_vsyscall () No symbol table info available. #1 0x00da3d33 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 No symbol table info available. #2 0x00df7f2f in g_cond_timed_wait_posix_impl (cond=0xb6007518, entered_mutex=0xabedc08, abs_time=0xafdd41a8) at gthread-posix.c:242 Timeout exceeded: 60 second, killing gdb Debuginfo absent: 696c53dec94174b9576589f9ad17d68cf108290d How to reproduce ----- 1. I had just installed additional module 2. program ended 3.
Created attachment 476296 [details] File: backtrace
There is really not a lot in the attached backtrace to know why the program crashed. Are you able to start Xiphos (without it crashing) after this particular crash occurred?
Yes. It seems to have been a fluke. I have not tried downloading additional modules, so I don't know if it will happen again. This was on an Asus EeePC 900 running Fedora 14 Linux. I will try getting another module and see if this repeats. I suspect it will not. Additional: I just tried it. It seems to have worked fine. This may have been an oddball glitch, and can probably be closed, so I am marking the status as such.