abrt 1.0.0 detected a crash. How to reproduce ----- 1. call 'aspell dump personal' by user with no personal dictonary. 2. 3. Comment: i have installed aspell and aspell-ru dict. i tried to dump dictionary using command above and it make a coredump instead of dict dump :) backtrace ----- Debuginfo absent: 0e779f0ad79e5478e077924603db4267836373eb Debuginfo absent: 5fcf523304c40f9ce6a77696af931cf3bba37e0e Debuginfo absent: 68354843e5200f56efe06888e9c389ee1e43aca2 Debuginfo absent: 9f32d8797542fdd3bac5f0a260c67076fdcce949 Debuginfo absent: 9feb0c25009cf269edc39e1712fc28b8fc71e4ba Debuginfo absent: abf1248c4f583ec57845323e37fc0fb47ea50f48 Debuginfo absent: b329a97458f5692d53edfe12ef412c63ebdd2b6e Debuginfo absent: b33db28f22aab7373673ecf02e39f484051a134c Debuginfo absent: c181d25bcd3fc23903723c02b58a9fec0076d12f Debuginfo absent: db35e1ccd57ac6bd99dcfc37b1e86a48849be03c Core was generated by `aspell dump personal'. Program terminated with signal 6, Aborted. #0 0x00679416 in __kernel_vsyscall () Thread 1 (Thread 2172): #0 0x00679416 in __kernel_vsyscall () No symbol table info available. #1 0x00439a81 in raise () from /lib/libc.so.6 No symbol table info available. #2 0x0043b34a in abort () from /lib/libc.so.6 No symbol table info available. #3 0x00849fbd in acommon::PosibErrBase::handle_err() const () from /usr/lib/libaspell.so.15 No symbol table info available. #4 0x0805d3a8 in acommon::PosibErrBase::destroy() () No symbol table info available. #5 0x0804f59e in acommon::ObjStack::new_chunk() () No symbol table info available. #6 0x0805cdde in acommon::ObjStack::new_chunk() () No symbol table info available. #7 0x00425bb6 in __libc_start_main () from /lib/libc.so.6 No symbol table info available. #8 0x0804d0c1 in acommon::ObjStack::new_chunk() () No symbol table info available. cmdline: aspell dump personal component: aspell executable: /usr/bin/aspell kernel: 2.6.31.6-145.fc12.i686 package: aspell-12:0.60.6-7.fc12 rating: 3 reason: Process was terminated by signal 6
Created attachment 377599 [details] File: backtrace
*** Bug 591379 has been marked as a duplicate of this bug. ***
This bug is fixed in upstream version since 0.61 not released yet.