public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "roothorick at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/59474] New: Invalid binaries produced when making win32 EXEs with -gsplit-dwarf Date: Wed, 11 Dec 2013 16:57:00 -0000 [thread overview] Message-ID: <bug-59474-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59474 Bug ID: 59474 Summary: Invalid binaries produced when making win32 EXEs with -gsplit-dwarf Product: gcc Version: 4.8.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: debug Assignee: unassigned at gcc dot gnu.org Reporter: roothorick at gmail dot com This in mingw-builds MinGW: roothorick@MODESTMONSTER ~ $ cat test.c int main() { } roothorick@MODESTMONSTER ~ $ gcc -gsplit-dwarf -o test.exe test.c roothorick@MODESTMONSTER ~ $ ./test.exe sh: ./test.exe: Bad file number roothorick@MODESTMONSTER ~ $ gcc --version gcc.exe (rev5, Built by MinGW-W64 project) 4.8.1 Copyright (C) 2013 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
next reply other threads:[~2013-12-11 16:57 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-11 16:57 roothorick at gmail dot com [this message] 2014-04-05 6:06 ` [Bug debug/59474] " asmwarrior 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-59474-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).