Wei Ming Khoo

Hi, taintgrind does not include the autogen.sh script, but uses the one that comes with valgrind. Did you install valgrind (http://valgrind.org)?

If you don't want to replace the default installation, you can install it at location you specify using 'configure --prefix=...', which is what the taintgrind installation instructions describe. By the...

VEX, which is what valgrind uses, takes a little getting used to. However, if you include debugging symbols during compilation (e.g. gcc -g ...), taintgrind will list the source line....

Let's try and get taintgrind to build on MacOS.

Getting this error ../coregrind/link_tool_exe_darwin 0x158000000 gcc -o taintgrind-amd64-darwin -arch x86_64 -O2 -g -std=gnu99 -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wcast-align -Wcast-qual -Wwrite-strings -Wempty-body -Wformat -Wformat-security -Wignored-qualifiers -fno-stack-protector -fno-strict-aliasing -fno-builtin -Wno-cast-align...

Seems to compile for me on High Sierra amd64. Someone else want to give it a go? @tcullum-gpsw ?

Thanks for bringing up this issue. Could you provide a test case that demonstrates the issue?

At least for me, std::to_string is implemented by [_itoa.c](https://code.woboq.org/userspace/glibc/stdio-common/_itoa.c.html). ``` const char _itoa_upper_digits[36] = "0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ"; ... const char *digits = (upper_case? _itoa_upper_digits : _itoa_lower_digits); ... *--buflim = digits[value % Base];...

Do you have an example that I can look at?