gcc gnu C library Reference Manual

It took me some time to find out that the documentation of the newlib library is probably the document above.
I found it at
http://www.codesourcery.com/sgpp/lite/arm/portal/doc714/libc.pdf

I did not find however what the 'restrict' in the function below mean.


???

and in case this has no bearing on this try:


Why does this crash? (no error or warning)

You should check that you don't print a NULL value with %s.

Arrays ttname and ttvalue are useless here.
Pointers ttnm and ttval are initialized but are overwritten just after, receiving results of strtok.

I added debug printing (neither the printf Printf or DebugPrintF appear in the shell from which the programwas launched. Using
DumpDebugBuffer allowed me still to check where the crash appeared:

it is the first use of strtok, the
DebugPrintF("strtok done\n"); following immediately after the call was not executed.


I could be that the second call returns a NULL pointer instead of "that" , since "that" is not followed by a delimiter, but i don't see why the first call would fail to recognise "THIS"

Except for the mysterious 'restrict' qualifiers in the strtok definition i don't see what is wrong.

The restrict keyword is to do with the location that the pointer points at. Basically restrict tells the compiler that no other pointer is going to point at that memory block, so the complier can do more optimizations. See Wikipedia - restrict keyword. As for the problem you're having what happens if you do explicit checks for NULL returns from strtok?

According to http://sourceware.org/newlib/libc.html#strtok
there is no restrict qualifier for this command.

Simon

@billyfish

my first call to strtok now looks like


delimiters are printed OK, neither of the 2 other DebugPrintF's appear.
The GrimReapers crashlog seems to be the same as before

@JosDuchIt

You are trying to tokenize a constant string, which is impossible since strtok() will modify the string. The crash you are getting is because strtok() is trying to write to read-only memory. The crash log, which you never made public here, should have exposed this.

The man pages included in Ubuntu Linux contain these warnings for strtok():

Quote:

@tboeckel

Well spotted. Changing from a "char *" to a "char []" should fix it. Something like:


char str [] = "THIS=that@";
const char *delimiters = "=@";
char *ptr;
printf ("delimiters = %s\n", delimiters);

ptr = strtok (str, delimiters);
while (ptr)
{
printf ("strtok returned %s\n", ptr);

ptr = strtok (NULL, delimiters);
}

fflush (stdout);

@tboeckel and billyfish

Thanks.

In the mean time i had used strcpy to copy ptr to copyptr and discovered the perror() function.

Alas: using perror("strtok") i am told "function not implemented."

My next question is then : what functions are implemented in the Amiga OS4 NewLib? Is there a method to generate this list ?

I am still going to test billyfish'es solution adding perror("strtok")

Tested and was OK, seems that strtok() exists after all.


My "next" question above remains however.