On 29/08/18 22:16, Stefan Ram wrote:
> The successor of »srand( time( 0 ))« is supposed to be
>
> ::std::mt19937 algorithm{ ::std::random_device{}() };
>
> . But with MinGW, a random number generating algorithm
> initialized in this way always seems to produce the same
> sequence (AFAIK).
>
> GCC now has sanitizers for addresses and UB, but not
> when you use MinGW (AFAIK).
>
> GDB has a TUI (Ctrl-X A) and an embedded Python interpreter,
> just not when you use the GDB of MinGW (AFAIK).
>
> And then there's this requirement to sometimes #define
> »__USE_MINGW_ANSI_STDIO« just to get a compliant standard I/O
> (AFAIK).
>
> (I just had to write down this collection somewhere before
> I forget it.)
>
> (Of course, I /am/ grateful to the creators of MinGW that
> something like this is available for Windows at all.)
>
> And when do we get valgrind under Windows?
>
Just to be clear here - are you using gcc from the old
<
http://mingw.org/> site, or are you using the much newer and more
powerful <
http://mingw-w64.org/doku.php> version?
(It is entirely believable that this too has limitations. In
particular, the address sanitizers and leak detection work by fancy
games with virtual memory settings - these techniques may simply not
have equivalents in Windows.)