Hide Forgot
abrt version: 1.1.14 architecture: i686 cmdline: /usr/lib/openoffice.org3/program/swriter.bin -writer component: openoffice.org crash_function: _int_malloc executable: /usr/lib/openoffice.org3/program/swriter.bin kernel: 2.6.34.7-66.fc13.i686 package: openoffice.org-writer-1:3.2.0-12.33.fc13 rating: 4 reason: Process /usr/lib/openoffice.org3/program/swriter.bin was killed by signal 6 (SIGABRT) release: Fedora release 13 (Goddard) time: 1295973221 uid: 500 backtrace ----- [New Thread 8115] [New Thread 8119] [New Thread 8128] [New Thread 8129] [New Thread 8130] [New Thread 8131] [New Thread 8132] [New Thread 8133] [New Thread 8134] [New Thread 8135] [New Thread 8141] [New Thread 8142] [New Thread 8102] [New Thread 8103] [New Thread 8104] [New Thread 8105] [New Thread 8095] warning: "/var/cache/abrt-di/usr/lib/debug/.build-id/b0/92e943ad63f83804af87c5bc62b0c1a9610a8d.debug": separate debug info file has no debug info warning: "/var/cache/abrt-di/usr/lib/debug/.build-id/de/72a6d25a3d3e3c8b8c2eaa2d50ad7fb046a2d6.debug": separate debug info file has no debug info warning: "/var/cache/abrt-di/usr/lib/debug/.build-id/72/908c2613b36817a167220443e477d6daa86cb1.debug": separate debug info file has no debug info Core was generated by `/usr/lib/openoffice.org3/program/swriter.bin -writer'. Program terminated with signal 6, Aborted. #0 0x003c5416 in __kernel_vsyscall () Thread 17 (Thread 8095): #0 _int_malloc (av=0xa123a0, bytes=36) at malloc.c:4279 Timeout exceeded: 60 second, killing gdb How to reproduce ----- 1. 2. 3. Same ole same ole
Created attachment 475226 [details] File: backtrace
The backtrace is truncated and so doesn't reveal anything. Can you reproduce this, and if so how ?
That's the problem. The backtrace is always truncated. I have done everything the bug reporting tool tells me to do and have run the tests you people have asked me to run and provided the results. I used to to do this stuff so I know you can't do anything if you can't get it to replicate but I am at a loss here. I've had 6-8 crashes tonight while I tried to work on a project that I didn't even try to report because of the truncated backtrace problem. I've even rebooted (hey, it works for Microsoft/yuck sometimes). You tell me what to try and I'm willing to do it (don't be too much of a Smart butt please). If I wasn't under a deadline right now I'd upgrade to 14 but right now I have to stay with 13 so unless you guys come up with something else I bet you close this one and slap INSUFFICIENT INFORMATION on it like someone did my reports last week. Hey, like I said. I used to do you job and don't blame you at all. Keep up the good work guys and gals and if I can do anything to help just ask.
Well, you may try yum install abrt-cli debuginfo-install openoffice.org-core openoffice.org-writer abrt-cli -i 12a5847e4ef9de13c7c4ed1d8e45453bf755b245 -b . That will (hopefully) generate a new backtrace. I think abrt does no cleanup of the downloaded debuginfo files, but has a limit on size of the download dir, and you hit that limit :( If this is the case, rm -rf /var/cache/abrt-di/* should help.
Here's the backtrace I got after doing the above: [New Thread 2983] [New Thread 2987] [New Thread 2989] [New Thread 2990] [New Thread 2991] [New Thread 2992] [New Thread 2993] [New Thread 2994] [New Thread 2995] [New Thread 2996] [New Thread 2997] [New Thread 2998] [New Thread 2978] [New Thread 2979] [New Thread 2980] [New Thread 2981] [New Thread 2982] warning: "/usr/lib/debug/usr/lib/libicudata.so.42.1.debug": separate debug info file has no debug info warning: "/usr/lib/debug/usr/lib/openoffice.org/ure/lib/libstlport_gcc.so.debug": separate debug info file has no debug info warning: "/var/cache/abrt-di/usr/lib/debug/.build-id/72/908c2613b36817a167220443e477d6daa86cb1.debug": separate debug info file has no debug info Core was generated by `/usr/lib/openoffice.org3/program/swriter.bin -writer'. Program terminated with signal 6, Aborted. #0 0x003c5416 in __kernel_vsyscall () Thread 17 (Thread 2982): #0 0x003c5416 in __kernel_vsyscall () No symbol table info available. #1 0x0095bf56 in __poll (fds=0xb516c890, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 Timeout exceeded: 60 second, killing gdb
Hm, that's not much better :(
Frustrating I know, but what else can I do ?, all I've got here is "it crashes" with no indication as to where or how to reproduce it :-(