public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "asmwarrior at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug win32/14227] GDB CVS HEAD Build Error under MinGW Date: Wed, 13 Jun 2012 09:37:00 -0000 [thread overview] Message-ID: <bug-14227-4717-UwvbQsHSbr@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-14227-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=14227 asmwarrior <asmwarrior at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|gdb |win32 Summary|gdb hangs after entering |GDB CVS HEAD Build Error |mixed "n" and "bt" command |under MinGW --- Comment #1 from asmwarrior <asmwarrior at gmail dot com> 2012-06-13 09:37:15 UTC --- Oh, this hang problem is caused my own local patch to workaround the build failure on MinGW target. After I revert the three consecutive three commit by * 2012-06-11 Pedro Alves <palves@redhat.com> * serial.c (do_serial_close): Remove early return when SCB is null. Then, the gdb CVS head mingw build works Fine. So, I will change the title to "build error" on MinGW target. See: http://sourceware.org/ml/gdb/2012-06/msg00061.html -- 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-06-13 9:37 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-13 7:37 [Bug gdb/14227] New: gdb hangs after entering mixed "n" and "bt" command asmwarrior at gmail dot com 2012-06-13 9:37 ` asmwarrior at gmail dot com [this message] 2012-06-13 12:29 ` [Bug win32/14227] GDB CVS HEAD Build Error under MinGW asmwarrior at gmail dot com 2012-08-14 17:39 ` keiths at redhat dot com 2012-08-15 1:15 ` asmwarrior at gmail dot com 2012-08-15 14:30 ` 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-14227-4717-UwvbQsHSbr@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).