public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/14458] GDB on Pandaboard: can't single-step code (next) Date: Wed, 28 Nov 2012 17:59:00 -0000 [thread overview] Message-ID: <bug-14458-4717-0beom0l46c@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-14458-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=14458 Pedro Alves <palves at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at redhat dot com --- Comment #1 from Pedro Alves <palves at redhat dot com> 2012-11-28 17:59:22 UTC --- It's hard to tell what could be wrong. Things like these happening most frequently tend to be bugs in gdb's software single-step implementation (though those are rare nowadays), which you'd need to debug (look for arm_get_next_pc), or in the unwinders (step working, but "next" not, would be an indication), but it could also be a whole range of different other things. "set debug infrun 1" might shed some more light. -- 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.
prev parent reply other threads:[~2012-11-28 17:59 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-12 16:24 [Bug c++/14458] New: " redwindwanderer at gmail dot com 2012-11-28 17:10 ` [Bug gdb/14458] " tromey at redhat dot com 2012-11-28 17:59 ` palves at redhat dot com [this message]
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-14458-4717-0beom0l46c@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).