Description of problem:
I've got plasma-desktop crash catched by abrt, but when gdb was generating backtrace, it ate 3.5 GB ram which woke up oom killer.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
0.debuginfo-install kdebase-workspace-4.5.2-1.fc14.x86_64 (I have kde* packages directly from koji)
1.gdb -core coredump
2.use commands abrt uses for generating backtrace (I'll provide them later, because I'll have to ask abrt's maintainer)
gdb consumes 3.3 GB (vsz) and 2.68 GB (rsz)
less occupied memory
#14 in lookup_symbol_global (name=0xb652c4 "char", block=<value optimized out>, domain=VAR_DOMAIN) at ../../gdb/symtab.c:1448
It is the known problem of regression by the .gdb_index acceleration.
Tom Tromey is preparing .gdb_index version 3.
Tom has already checked it in, I missed that:
FYI: index pre-expansion fix
Resource allocation after loading a core file + symbols:
VSZ= 592284 RSS= 396856
gdb-7.2-22.fc14 has been submitted as an update for Fedora 14.
gdb-7.2-22.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update gdb'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/gdb-7.2-22.fc14
gdb-7.2-23.fc14 has been submitted as an update for Fedora 14.
gdb-7.2-23.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.