Re: relearning C: why does an in-place change to a char* segfault?

Path	csiph.com!eternal-september.org!feeder.eternal-september.org!nntp.eternal-september.org!.POSTED!not-for-mail
From	Keith Thompson <Keith.S.Thompson+u@gmail.com>
Newsgroups	comp.lang.c
Subject	Re: relearning C: why does an in-place change to a char* segfault?
Date	Mon, 02 Mar 2026 04:43:04 -0800
Organization	None to speak of
Lines	22
Message-ID	<875x7ee71j.fsf@example.invalid> (permalink)
References	<IoGcndcJ1Zm83zb7nZ2dnZfqnPWdnZ2d@brightview.co.uk> <v8fhhl$232oi$1@dont-email.me> <v8fn2u$243nb$1@dont-email.me> <87jzh0gdru.fsf@nosuchdomain.example.com> <v8gte2$2ceis$2@dont-email.me> <20240801174256.890@kylheku.com> <v8i9o8$2oof8$1@dont-email.me> <v8j808$2us0r$1@dont-email.me> <864j7oszhu.fsf@linuxsc.com> <87o75vg9ot.fsf@nosuchdomain.example.com> <86ikw1o0h8.fsf@linuxsc.com> <8734n5fjtq.fsf@nosuchdomain.example.com> <868qvc62h7.fsf@linuxsc.com> <87a5fssb70.fsf@nosuchdomain.example.com> <86tsuzeze4.fsf@linuxsc.com> <87zf4q99sh.fsf@example.invalid> <20260302102440.00004a5c@yahoo.com>
MIME-Version	1.0
Content-Type	text/plain
Injection-Date	Mon, 02 Mar 2026 12:43:05 +0000 (UTC)
Injection-Info	dont-email.me; posting-host="904fdc8ce99c4265d8d70c325ce3d825"; logging-data="1210434"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/vDnBSGS55rnOirUKvEfvn"
User-Agent	Gnus/5.13 (Gnus v5.13)
Cancel-Lock	sha1:28F5oKY0R5XFiRMtHzEGIHnl2gY= sha1:VCUiMqim0qOtAcTj2hdLm6WRSio=
Xref	csiph.com comp.lang.c:396727

Show key headers only | View raw

Michael S <already5chosen@yahoo.com> writes:
> On Sun, 01 Mar 2026 19:42:38 -0800
> Keith Thompson <Keith.S.Thompson+u@gmail.com> wrote:
>> Tim Rentsch <tr.17687@z991.linuxsc.com> writes:
[...]
>> > I see no reason to feel an obligation to know whether someone
>> > might feel insulted by something I say.
[...]
>> That's three times today that you've replied to a post I made a
>> long time ago (about a year and a half in this case).
>> 
>> I get the impression that you're stalking me.
>
> It is appreciation.

Do you speak for Tim?

[...]

-- 
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
void Void(void) { Void(); } /* The recursive call of the void */

Back to comp.lang.c | Previous | Next — Previous in thread | Find similar

Thread

Re: relearning C: why does an in-place change to a char* segfault? Tim Rentsch <tr.17687@z991.linuxsc.com> - 2026-03-01 18:30 -0800
  Re: relearning C: why does an in-place change to a char* segfault? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-03-01 19:42 -0800
    Re: relearning C: why does an in-place change to a char* segfault? Michael S <already5chosen@yahoo.com> - 2026-03-02 10:24 +0200
      Re: relearning C: why does an in-place change to a char* segfault? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-03-02 04:43 -0800

csiph-web