[Bug gdb/11555] New: 100% CPU for minutes trying to print expresion

["jlquinn at us dot ibm dot com" <sourceware-bugzilla at sourceware dot org>]

I've build gdb 7.1 on Centos 5.4 x86_64 using the system compiler.  I'm trying
to debug a c++ application and moved to 7.1 to get past issues in 6.8.  However,
when I stop and try to print an expression, it literally takes minutes for gdb
to come back with the answer on a 4 core 3GHz server.

A snapshot is below.  The vector below is standard stl vector and tokenOffset is
just a struct.  I C-c'd it after 3 minutes.  It will eventually print the right
answer, but it takes a ridiculous amount of time.

6.8 and 7.0.1 work as expected on the same debug binaries.  I built 7.0.1 out of
the box as well as 7.1.  6.8 is the system gdb.


537       vector<tokenOffset> toks;
(gdb) 
539       unsigned prev_type = TOK_WHITESPACE;
(gdb) p toks.size()
Quit
(gdb) show ver
verbose  version  
(gdb) show version 
GNU gdb (GDB) 7.1
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
(gdb)

-- 
           Summary: 100% CPU for minutes trying to print expresion
           Product: gdb
           Version: 7.1
            Status: UNCONFIRMED
          Severity: critical
          Priority: P2
         Component: gdb
        AssignedTo: unassigned at sourceware dot org
        ReportedBy: jlquinn at us dot ibm dot com
                CC: gdb-prs at sourceware dot org
 GCC build triplet: x86_64-unknown-linux-gnu
  GCC host triplet: x86_64-unknown-linux-gnu
GCC target triplet: x86_64-unknown-linux-gnu


http://sourceware.org/bugzilla/show_bug.cgi?id=11555

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.