Hide Forgot
abrt version: 1.1.14 architecture: i686 cmdline: xiphos component: xiphos executable: /usr/bin/xiphos kernel: 2.6.35.10-74.fc14.i686 package: xiphos-3.1.4-1.fc14 reason: Process /usr/bin/xiphos was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1296871943 uid: 500 backtrace ----- [New Thread 4066] [New Thread 4067] [New Thread 4068] [New Thread 4069] [New Thread 4070] [New Thread 4071] [New Thread 4072] [New Thread 4083] [New Thread 4084] [New Thread 4085] [New Thread 4087] [New Thread 4089] [New Thread 4106] [New Thread 4107] [New Thread 4108] [New Thread 6580] [New Thread 7365] [New Thread 7366] [New Thread 7367] Core was generated by `xiphos'. Program terminated with signal 11, Segmentation fault. #0 0x080a19b1 in BackEnd::get_entry_attribute (this=0xae4d8d8, level1=0x80e0d6b "Heading", level2=0x80e0d62 "Preverse", level3=0xbfbd5c64 "0") at ../src/backend/sword_main.cc:655 Timeout exceeded: 60 second, killing gdb comment ----- This is the second time I have had the program end while working with modules. Last time was while I was working with indexing modules. I do not know how to make it end deliberately. System is Fedora 14 on an EeePC 900 (Celeron processor). How to reproduce ----- 1. I was changing my selection of modules for parallel view. 2. program ended abruptly 3.
Created attachment 477157 [details] File: backtrace
This seems to now be a moot point. Current version is xiphos-3.1.4-8, at least in the Fedora 15 repository. It has not exhibited this behavior.