Strtok () daemon which is not how it used up? Char = memo->;precieve; *precieve Seps[] char = "; " Char = NULL; *token LEAVES OF 13 SPECIES OF LAURACEAE Establish string and get the first token : */ Syslog (LOG_ERR, precieve); Syslog (LOG_ERR, seps); Syslog (LOG_ERR, "before strtok"); Token = strtok (precieve, seps); Syslog (LOG_ERR, "after strtok"); Print can be seen from the log : Nov 2 : 11:31:00 LinuxAS3 limmd[5314] zhouxw;liangjh Nov 2 LinuxAS3 limmd[5314] : 11:31:00; Nov 2 11:31:00 LinuxAS3 limmd[5314] : before strtok Now, little or nothing Can be seen in the implementation of token = strtok (precieve, seps); Often wrong But this code which is a normal procedure in the ordinary ah, there would not be decrypted Why? If there debugging with GDB of this encryption, how make? Strtok () daemon which is not how it used up? May be your dameon closed STDIN & STDOUT Strtok () daemon which is not how it used up? Please confirm encryption using locale-related environmental variables, such LANG, LC_ALL, if you set up the other characters, all related to the string, the token will have a different function performance Strtok () daemon which is not how it used up? The strtok () function is Unsafe in multithreaded applica- Tions. The strtok_r () function should be used instead. I generally used to replace strtok : sscanf { Char s1[16], s2[16]; *msg Char = "abc:def"; Sscanf (msg, "%[^:]:%s" s1, s2); } [ Closed window ]