Description of problem: GDB has a testsuite regression. Version-Release number of selected component (if applicable): FAIL glibc-2.12.90-19.x86_64 PASS glibc-2.12.90-18.x86_64 How reproducible: Always Steps to Reproduce: Compile FSF GDB HEAD, from: git clone git://sourceware.org/git/gdb.git cd gdb/testsuite make site.exp runtest gdb.base/completion.exp Actual results: Running ./gdb.base/completion.exp ... ERROR: Process no longer exists FAIL: gdb.base/completion.exp: (timeout) complete-command 'file ./gdb.base/compl' FAIL: gdb.base/completion.exp: (timeout) complete 'file ./gdb.base/complet' FAIL: gdb.base/completion.exp: (timeout) complete 'info func marke' FAIL: gdb.base/completion.exp: (timeout) complete 'set follow-fork-mode' ERROR: Couldn't send complete print values[0].x. to GDB. ERROR: Couldn't send complete sav to GDB. ERROR: Couldn't send complete save-t to GDB. === gdb Summary === # of expected passes 27 # of unexpected failures 4 # of expected failures 1 # of unresolved testcases 4 Expected results: Running ./gdb.base/completion.exp ... === gdb Summary === # of expected passes 35 # of expected failures 1 Additional info: Feel free to NEEDINFO it to track down the specific glibc regression. processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Core(TM) i7 CPU @ 9200 @ 2.67GHz stepping : 5 cpu MHz : 2793.000 cache size : 8192 KB physical id : 0 siblings : 8 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips : 5397.08 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: [There are 8 CPUs - 4 + x2 by hyperthreading.]
Really a memory corruption by GDB - it just did not reproduce before, sorry. [commit] Fix .gdb_index memory corruption http://sourceware.org/ml/gdb-patches/2010-11/msg00216.html
gdb-7.2-26.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/gdb-7.2-26.fc14
gdb-7.2-26.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-26.fc14
gdb-7.2-26.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.