public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/14647] [x32] "next" doesn't work with -O -g Date: Sat, 29 Sep 2012 23:24:00 -0000 [thread overview] Message-ID: <bug-14647-4717-6NjClJ0bsB@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-14647-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=14647 --- Comment #1 from H.J. Lu <hjl.tools at gmail dot com> 2012-09-29 23:24:12 UTC --- hjl/x32/gdb_7_4-branch git branch at http://sourceware.org/git/?p=gdb.git;a=summary works fine. -- 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-09-29 23:24 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-29 19:13 [Bug gdb/14647] New: " hjl.tools at gmail dot com 2012-09-29 23:24 ` hjl.tools at gmail dot com [this message] 2012-10-01 16:13 ` [Bug gdb/14647] " jan.kratochvil at redhat dot com 2012-10-01 16:30 ` hjl.tools at gmail dot com 2012-10-15 20:37 ` cvs-commit at gcc dot gnu.org 2012-11-10 0:50 ` cvs-commit at gcc dot gnu.org 2012-11-10 0:52 ` hjl.tools 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-14647-4717-6NjClJ0bsB@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).