public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "timblaktu at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug mi/9831] very slow loading of symbols under mi2 & core dumps Date: Sat, 22 Jan 2011 01:24:00 -0000 [thread overview] Message-ID: <bug-9831-4717-0zEucj3aYa@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-9831-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=9831 timblaktu at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |timblaktu at gmail dot com --- Comment #5 from timblaktu at gmail dot com 2011-01-22 01:23:59 UTC --- I 'm experiencing a possibly similar problem using gdb 7.0.1-debian. This problem does not happen when debugging my app via command line - it only happens when using gdb MI via eclipse. Here is the problem: When I enter main(), eclipse issues a 543,915 20-stack-list-locals --thread 1 --frame 0 1 MI command to gdb, and it hangs for about a minute. Then the response comes back and seems to contain correct data. Then I can single step again, but when I do, the same process repeats. Each time it hangs, top on linux tells me that there is a "gdb --interpreter mi2 --nx" process that is hogging a core on my machine. I have #ifdef stubbed out code in main() until I have a simple case that hangs and a simple case that doesn't hang. The only difference is the inclusion of one more source line that declares/initializes a struct local variable. There is nothing very peculiar about this struct. Everything else looks the same for the good and bad case. Again, this behavior does not happen when debugging the same app via gdb command line and printing the locals. It seems MI-specific. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next parent reply other threads:[~2011-01-22 1:24 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-9831-4717@http.sourceware.org/bugzilla/> 2011-01-22 1:24 ` timblaktu at gmail dot com [this message] 2011-01-22 2:01 ` timblaktu at gmail dot com 2011-12-14 16:01 ` dje at google dot com 2023-01-23 19:50 ` tromey at sourceware dot org 2009-02-09 22:11 [Bug mi/9831] New: " daniel dot santos at pobox dot com 2009-02-09 23:08 ` [Bug mi/9831] " daniel dot santos at pobox dot com 2009-04-12 17:12 ` tromey at redhat dot com 2009-04-14 3:13 ` daniel dot santos at pobox dot com 2009-04-14 16:26 ` tromey at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-9831-4717-0zEucj3aYa@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).