🚀 go-pugleaf

In article <59vbmi$9i0@nntpb.cb.lucent.com>, M.Wang <xiaofei@lucent.com> wrote:
>what is wrong with the following program?

This is a forum for reporting GCC bugs, not a C programming help forum. I
think you want comp.lang.c or gnu.gcc.help.

>#include <stdio.h>
>#include <string.h>
>
>int
>main()
>{
>strtok("a b c", " ");
>return 0;
>}

This is not a valid ANSI C program, because attempting to modify string
literals is prohibited and invokes undefined behavior. Many UNIX
implementations of the C language take advantage of this constraint and
place string literals in memory pages that are marked as read-only
(for example, string literals may be interspersed throughout the code
section of the executable).

You have not exposed a GCC bug.  A compiler bug is exposed when a *correct*
program fails to translate and execute properly.