public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "ppluzhnikov at google dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug breakpoints/10852] command sequences interrupted unexpectedly Date: Thu, 10 May 2012 23:07:00 -0000 [thread overview] Message-ID: <bug-10852-4717-KnMnIPY6cF@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-10852-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=10852 --- Comment #3 from Paul Pluzhnikov <ppluzhnikov at google dot com> 2012-05-10 23:06:39 UTC --- Over on stackoverflow, someone suggested a workaround: http://stackoverflow.com/a/10529068/50617 A 2nd work around that doesn't require python appears to be defining a new gdb command and running that in commands: define foo print *i set $addrOfI = i finish print *$addrOfI end break doSomething commands foo end -- 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:[~2012-05-10 23:07 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-10852-4717@http.sourceware.org/bugzilla/> 2012-05-10 23:07 ` ppluzhnikov at google dot com [this message] 2020-10-31 17:47 ` tromey at sourceware dot org 2020-10-31 17:49 ` tromey at sourceware dot org 2023-10-27 18:31 ` ratmice at gmail dot com 2023-10-27 21:45 ` g_sauthoff at web dot de 2009-10-26 19:08 [Bug breakpoints/10852] New: " ppluzhnikov at google dot com 2009-10-31 17:55 ` [Bug breakpoints/10852] " ppluzhnikov at google dot com 2010-02-26 3:08 ` tyl dot ero dot d dot erkirk at gmail 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-10852-4717-KnMnIPY6cF@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).