abrt version: 1.1.17 architecture: x86_64 Attached file: backtrace, 12979 bytes cmdline: gdb upx.out component: gdb Attached file: coredump, 20230144 bytes crash_function: get_frame_type executable: /usr/bin/gdb kernel: 2.6.35.11-83.fc14.x86_64 package: gdb-7.2-46.fc14 rating: 4 reason: Process /usr/bin/gdb was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1301078289 uid: 500 comment ----- (gdb) list 141 if (!isOpen() || len < 0) 142 throwIOException("bad read"); 143 errno = 0; 144 long l = acc_safe_hread(_fd, buf, len); 145 if (errno) *146 throwIOException("read error",errno); 147 return (int) l; 148 } 149 150 (gdb) p errno Segmentation fault (core dumped) How to reproduce ----- 1. (gdb) p errno 2. 3.
Created attachment 487642 [details] File: backtrace
gdb-7.2-51.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/gdb-7.2-51.fc14
+gdb-7.2.50.20110328-32.fc15
Package gdb-7.2-51.fc14: * should fix your issue, * was pushed to the Fedora 14 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gdb-7.2-51.fc14' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/gdb-7.2-51.fc14 then log in and leave karma (feedback).
gdb-7.2-51.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.