public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "siebert at aicas dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/48866] New: gcc hangs when -g is set Date: Wed, 04 May 2011 08:56:00 -0000 [thread overview] Message-ID: <bug-48866-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48866 Summary: gcc hangs when -g is set Product: gcc Version: 4.4.4 Status: UNCONFIRMED Severity: major Priority: P3 Component: debug AssignedTo: unassigned@gcc.gnu.org ReportedBy: siebert@aicas.com Created attachment 24178 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24178 Minimum C example I could produce. The original code was generated C code. gcc hangs when compiling the attached C source code (on Linux/x86) as follows > gcc -O2 -c test.c -o test.o -g [hangs forever...] ^C > The problem disappears without -g or when using -O0. > gcc -O2 -c test.c -o test.o > gcc -O0 -c test.c -o test.o -g >
next reply other threads:[~2011-05-04 8:56 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-04 8:56 siebert at aicas dot com [this message] 2011-05-04 10:37 ` [Bug debug/48866] " paolo.carlini at oracle dot com 2011-05-04 11:43 ` rguenth at gcc dot gnu.org 2011-05-04 12:08 ` jakub at gcc dot gnu.org 2011-05-04 14:28 ` jakub at gcc dot gnu.org 2011-05-05 11:56 ` aoliva at gcc dot gnu.org 2011-05-05 13:06 ` aoliva at gcc dot gnu.org 2011-05-05 13:55 ` jakub at gcc dot gnu.org 2011-05-06 14:45 ` aoliva at gcc dot gnu.org 2011-05-06 22:30 ` aoliva at gcc dot gnu.org 2011-05-07 6:16 ` jakub at gcc dot gnu.org 2011-05-07 6:37 ` jakub at gcc dot gnu.org 2012-04-13 15:57 ` aoliva at gcc dot gnu.org 2012-06-13 20:42 ` aoliva at gcc dot gnu.org 2012-06-28 7:40 ` aoliva at gcc dot gnu.org
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-48866-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).