abrt version: 1.1.14 architecture: x86_64 Attached file: backtrace cmdline: gdb -batch -ex 'set debug-file-directory /usr/lib/debug:/var/cache/abrt-di/usr/lib/debug' -ex 'file /usr/bin/evolution' -ex 'core-file /var/spool/abrt/ccpp-1293092226-3787/coredump' -ex 'thread apply all backtrace 2048 full' -ex 'info sharedlib' -ex 'print (char*)__abort_msg' -ex 'print (char*)__glib_assert_msg' -ex 'info registers' -ex disassemble component: gdb executable: /usr/bin/gdb kernel: 2.6.35.11-83.fc14.x86_64 package: gdb-7.2-41.fc14 reason: Process /usr/bin/gdb was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) time: 1297778100 uid: 1424 How to reproduce ----- 1.generate automatic bug reporting bug 2. 3.
Created attachment 478879 [details] File: backtrace
Package: gdb-7.2-41.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. reporting bug ID677759 2. 3.
Package: gdb-7.2-41.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. reporting bug id=677767 2. 3.
Package: gdb-7.2-41.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I try to put a breakpoint wharn debugging a program Maybe selinux related?
I do not think it is SELinux related. Do you have it reproducible? It should get fixed by changing the iterator from libthread_db to /proc/PID/task/ readdir, which is planned for some years.
Sorry, I can't reproduce it. But I have another strange behaviour maybe related: I can't set breakpoints, this is the error: "Cannot insert breakpoint 1. Error accessing memory address 0x3b24481778: Input/output error."
(In reply to comment #6) > "Cannot insert breakpoint 1. > Error accessing memory address 0x3b24481778: Input/output error." This error is known but one needs a reproducer. For example GDB may erroneously compute invalid address of a breakpoint where is no memory mapped. This one can be due to SELinux I think, you should check your /var/log/* (/var/log/messages probably).
I disabled selinux (SELINUX=permissive in /etc/selinux/config) and the problem persist, should I fill a different bug?
It is enough + easier to just run `setenforce 0' for such test. Yes, the `Error accessing memory address' is unrelated to this Bug. We need a reproducer of that error message to be able to do anything with it.
ok, submitted a different bug about this issue in bug #678098
Package: gdb-7.2-41.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. while reporting a bug it just crashed
Could you send the core file GDB was trying to backtrace/report?
Package: gdb-7.2-41.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. start sending automatic bug report for pulseaudio 2. 3. Comment ----- this crash occurred while the automatic bug reporting tool was gathering debug stuff for a pulseaudio crash
Package: gdb-7.2-41.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. while debugging fortran code from scilab (www.scilab.org) 2. put a break on fortran code 3. on break gdb crash.
should be related to bug 654331
*** Bug 679268 has been marked as a duplicate of this bug. ***
*** Bug 674120 has been marked as a duplicate of this bug. ***
[patch 2/3] Fix threading internal error on corrupted memory http://sourceware.org/ml/gdb-patches/2011-02/msg00674.html
gdb-7.2-45.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/gdb-7.2-45.fc14
gdb-7.2-45.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-45.fc14
*** Bug 680307 has been marked as a duplicate of this bug. ***
Package: gdb-7.2-41.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.ran chkrootkit 2. crashed 3. no profit :( Comment ----- tried to run chkrootkit under system tools... failed!
Package: gdb-7.2-41.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. No idea how gdb crashed 2. 3.
Package: gdb-7.2-41.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.after installation gdb crashed 2. 3.
Package: gdb-7.2-41.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. try to send another bug report via abrt :) 2. 3.
gdb-7.2-45.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.