Hi,
Dan Kegel wrote:
>did you try the --track-origins option?
That looks like an exact fit, thank you.
Well, this option is not present in Ubuntu Intrepid's Valgrind.
In Ubuntu Lucid, the option is present but Valgrind does not
complain about wine_cp_wcstombs there.
I conclude it was likely a fa
> Hi,
>
> running the MCI tests with Valgrind generates a lot of output like follows
>
> ==13170== Use of uninitialised value of size 4
> ==13170==at 0x4035369: wine_cp_wcstombs (wctomb.c:147)
> ...[every line from 148 to 161]
> ==13170== Use of uninitialised value of size 4
> ==13170==at 0
Hi Joerg,
did you try the --track-origins option? That can sometimes give more detail
(see e.g. the traces in this old message):
On Thu, Jul 31, 2008 at 10:14 AM, Dan Kegel wrote:
> Hi Colin,
> your change
> http://source.winehq.org/git/wine.git/?a=commitdiff;h=c2c1a55f1c08f35ae02b811d1141acd6ec
Hi,
running the MCI tests with Valgrind generates a lot of output like follows
==13170== Use of uninitialised value of size 4
==13170==at 0x4035369: wine_cp_wcstombs (wctomb.c:147)
...[every line from 148 to 161]
==13170== Use of uninitialised value of size 4
==13170==at 0x403550A: wine_c
