public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: neil@gcc.gnu.org To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/5033: non const char *'s initial pointee data left on read only segment, causes seg. fault. Date: Thu, 06 Dec 2001 06:36:00 -0000 [thread overview] Message-ID: <20011206143601.14994.qmail@sources.redhat.com> (raw) The following reply was made to PR c/5033; it has been noted by GNATS. From: neil@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, rs025019@se.ritsumei.ac.jp Cc: Subject: Re: c/5033: non const char *'s initial pointee data left on read only segment, causes seg. fault. Date: 6 Dec 2001 14:31:50 -0000 Synopsis: non const char *'s initial pointee data left on read only segment, causes seg. fault. State-Changed-From-To: open->closed State-Changed-By: neil State-Changed-When: Thu Dec 6 06:31:49 2001 State-Changed-Why: Not a bug. This is not a property of the type assigned to, it is a property of the type of string literals. See -fwritable-strings and -Wwrite-strings in the manual. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=5033&database=gcc
next reply other threads:[~2001-12-06 14:36 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-12-06 6:36 neil [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-12-06 6:31 neil 2001-12-06 4:26 rs025019
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=20011206143601.14994.qmail@sources.redhat.com \ --to=neil@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).