[Bug gdb/21462] New: gdb hangs when pretty printing some variables in eclipse cdt

["smark at datto dot com" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=21462

            Bug ID: 21462
           Summary: gdb hangs when pretty printing some variables in
                    eclipse cdt
           Product: gdb
           Version: 7.12.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: smark at datto dot com
  Target Milestone: ---

Created attachment 10039
  --> https://sourceware.org/bugzilla/attachment.cgi?id=10039&action=edit
a list of stack traces from spinning gdb, plus a bit of the eclipse gdb log

I wrote up a question here which basically states the problem, and somebody
suggested posting to the mailing list, but I didn't see how, so I thought I'd
open a bug.

http://stackoverflow.com/questions/43743703/anybody-have-a-workaround-for-gdb-hanging-while-rendering-pretty-print-in-eclips

I've updated to eclipse neon, I svn updated to the latest
svn://gcc.gnu.org/svn/gcc/trunk/libstdc++-v3/python, and I've just built gdb
7.12.1, all the latest stuff, doesn't help.

I have the pretty printing all working, but every once in a while, trying to
update the variables view, gdb will hang. Actually it spins the cpu. I've
attached gdb to gdb (because I find the idea amusing) and have gotten a number
of stack traces and they're all implying some failure to find a printer and
retrying over and over. Anybody ever see this or have a workaround? It's not
obvious which printer (if it's a single one) is causing the problem, or I'd
just disable it.

Suggestions on how to even diagnose what printer to disable? I google and
google and nobody complains of this behaviour, but having reinstalled
everything, I don't get why it's not happening to anybody else.

Last time I ran into the problem I got some more stack traces and it eventually
hung in one spot. See the attached text file of stack traces.

-- 
You are receiving this mail because:
You are on the CC list for the bug.