public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pgunreben at lucent dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/25365] g++ crashes with segmentation fault, when -Wall is active Date: Mon, 12 Dec 2005 12:00:00 -0000 [thread overview] Message-ID: <20051212120022.28081.qmail@sourceware.org> (raw) In-Reply-To: <bug-25365-11866@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from pgunreben at lucent dot com 2005-12-12 12:00 ------- it doesn't crash, if I use the union in the code, e.g.: =============8<================= int main() { void *p; p = int32_t_incorrect; return 0; } =============8<================= -- pgunreben at lucent dot com changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|g++ crashes with |g++ crashes with |segmentation fault, when - |segmentation fault, when - |Wall is active |Wall is active http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25365
next prev parent reply other threads:[~2005-12-12 12:00 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-12-12 11:45 [Bug c++/25365] New: " pgunreben at lucent dot com 2005-12-12 12:00 ` pgunreben at lucent dot com [this message] 2005-12-12 15:04 ` [Bug c++/25365] " pinskia at gcc dot gnu dot 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=20051212120022.28081.qmail@sourceware.org \ --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).