Fwd: Valgrind and wine (was: re: Bug 4289: Debugging and dissasembly)

[James Trotter]

On 1/14/06, Robert Shearman <rob at codeweavers.com> wrote:
>
> Dan Kegel wrote:
>
> >Rob wrote:
> >
> >
> >>This very much looks like a use-after-free bug. The first two
> >>instructions are probably a COM *_Release call. Judging by the fact that
> >>this is a regression I would also guess that it is a Wine object.
> >>
> >>
> >
> >This sounds like a job for valgrind!
> >
> >But, er, does valgrind still work with wine?  Rob said it did in March:
> > http://www.winehq.com/hypermail/wine-devel/2005/03/0397.html
> >It was too hard for one guy back in July:
> >http://www.winehq.com/hypermail/wine-devel/2005/07/0401.html
> >but that was probably because he didn't see Rob's message from March.
> >Maybe we need to put better instructions on how to use
> >Valgrind with Wine on winehq.org... or, dare I suggest it,
> >bundle valgrind with Wine so anybody could easily use it
> >be setting WINEDEBUG=+valgrind or something like that...
> >
>
> Valgrind 3.1.0 works with Wine with no Wine modifications needed.
> However, one patch to valgrind is required to generate meaningful
> backtraces and I've attached it to this message - I guess I should
> report this to the valgrind developers.
>
> --
> Rob Shearman
>
>
>
>
>
>
>
>
I was really just considering using valgrind! I already have it installed,
but I wasn't sure it would work very nicely, though. I was afraid there
would be too much pointless output to wade through, but I'll try it tomorrow
sometime.

Cheers,
James
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.winehq.org/pipermail/wine-devel/attachments/20060114/2fd5344e/attachment.htm