* Bernhard R. Link <brlink@...> [110803 12:17]:
> Looking at dsc_strncmp I see nothing that could explain why
> a difference like that could have effects like that.
> As it does this funny malloc/free every time (no idea why
> it does that as it could just to strncasecmp(s1, s2, n-1))
> that might mean that there simply is some harvoc going on
> with the memory mangement code. Optimising that function to
> not do the temporary copy makes the bug disappear, but that
> might simply be a code moves around effect....
Actually, the bug still show up with the malloc/free/strncpy
removed with the following patch:
In other words: I'm totally at loss how this effect can
cause this. I will try to run it in the debugger with some
read watchpoints for the changed parts to see where it can
have a difference, but ....