| Summary: | [abrt] openoffice.org-writer-1:3.2.0-12.33.fc13: _int_malloc: Process /usr/lib/openoffice.org3/program/swriter.bin was killed by signal 6 (SIGABRT) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Paul M. Summitt <psummitt> | ||||
| Component: | openoffice.org | Assignee: | Caolan McNamara <caolanm> | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 13 | CC: | caolanm, dtardon | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:12a5847e4ef9de13c7c4ed1d8e45453bf755b245 | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-02-16 16:26:32 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Paul M. Summitt
2011-01-25 17:41:08 UTC
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 :-( |