Re: [Valgrind-users] m_libcbase.c compiler warnings

2018-01-09 Thread Jacek M. Holeczek
Dear Sirs, * and we have a bunch of other places where a similar strtok_r loop > is used, with similar variables not initialised. I do not know what is so "specific" about these two places but these are the only ones which generate any compiler warnings. Best regards, Jacek. ---

Re: [Valgrind-users] m_libcbase.c compiler warnings

2018-01-09 Thread Philippe Waroquiers
The compiler warning messages look somewhat fishy: * they speak about a variable (e.g. tokens_saveptr) but pointing at a line in a function where there is no such variable (e.g. the 'for (p = s' loop). * Maybe this is because the compiler does not understand strtok_r. Here is an ext

[Valgrind-users] m_libcbase.c compiler warnings

2018-01-09 Thread Jacek M. Holeczek
Dear Sirs, this is Ubuntu 14.04.5 LTS / x86_64 / gcc (Ubuntu 4.8.4-2ubuntu1~14.04.3) 4.8.4. While compiling the most current GIT version (as of today), I get some warnings: -- gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I