public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "alves.ped at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug python/13473] step N/next N does not trigger gdb.events.stop Date: Wed, 04 Jan 2012 13:08:00 -0000 [thread overview] Message-ID: <bug-13473-4717-e7wHcgJAew@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-13473-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=13473 --- Comment #2 from Pedro Alves <alves.ped at gmail dot com> 2012-01-04 13:07:26 UTC --- Thanks, the patch looks good. I'll see about adding a new test case so we don't regress in the future, and applying it to the source tree. -- 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 prev parent reply other threads:[~2012-01-04 13:08 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-06 22:19 [Bug python/13473] New: " khooyp at cs dot umd.edu 2011-12-06 22:37 ` [Bug python/13473] " khooyp at cs dot umd.edu 2012-01-03 21:55 ` tromey at redhat dot com 2012-01-04 10:47 ` alves.ped at gmail dot com 2012-01-04 13:08 ` alves.ped at gmail dot com [this message] 2012-01-05 13:16 ` alves.ped 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-13473-4717-e7wHcgJAew@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).