From: Richard Bos <rlb@hoekstra-uitgeverij.nl>
To: 9fans@cse.psu.edu
Subject: [9fans] Re: constant string
Date: Mon, 8 Mar 2004 10:53:36 +0000 [thread overview]
Message-ID: <404c460f.500459755@news.individual.net> (raw)
In-Reply-To: <pan.2004.03.07.05.32.00.621137@hotpop.com>
Prem Mallappa <prem_mallappa@hotpop.com> wrote:
> #include <stdio.h>
>
> int main(void)
> {
> char *s = "Hello";
>
> s[2] = 'z';
>
> printf ("%s\n", s);
>
> return 0;
> }
> my question is when i compile this in Linux (gcc) i get a segmentation
> fault at the second statement of main(),
> As far as my knowledge i think this is because in 2nd chapter of K&R book
> it is being mentioned that
> ' any thing enclosed between " and " is a string constant' so here i am
> changing a constant, and i get a segmentation fault ( and i also noticed
> that gcc stores the string Hello in read-only datasegment)
<http://www.eskimo.com/~scs/C-faq/q1.32.html>. Basically, yes, you're
correct.
> but when i compile the same thing in plan9 C compiler ( both native "8c"
> and "pcc" i get a output of "Hezlo")
> why this is happenning..
To begin with, IIRC Plan 9 C isn't exactly ISO C. But in any case,
assigning to a constant (in those cases where you don't get a mandatory
warning, and when you ignore the warning and do the assignment anyway,
as well) invokes undefined behaviour. This means that the implementation
is free to behave as it chooses to; this includes crashing, behaving as
if it were correct code, and anything in between.
Richard
next prev parent reply other threads:[~2004-03-08 10:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 10:15 [9fans] " Prem Mallappa
2004-03-08 10:27 ` lucio
2004-03-08 10:53 ` Richard Bos [this message]
2004-03-08 14:13 ` dbailey27
2004-03-08 15:22 ` C H Forsyth
2004-03-09 3:41 ` Russ Cox
2004-03-09 9:17 ` Charles Forsyth
2004-03-08 22:40 ` William Josephson
2004-03-10 9:47 ` [9fans] " Peter Pichler
2004-03-12 8:56 ` Bruce Ellis
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=404c460f.500459755@news.individual.net \
--to=rlb@hoekstra-uitgeverij.nl \
--cc=9fans@cse.psu.edu \
/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: link
Be 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 NNTP newsgroup(s).