Eric Pouech wrote:
If I assume that any decent user should report this type of error, I
only counted 2 reports (yours, and Shachar on some other topics),
Actually, if you'll read between the lines, you'll see this has been
bugging me as well. That's the reason I sent you a diff of two runs,
rath
Hi
--- Mike Hearn <[EMAIL PROTECTED]> wrote:
> OK, bear in mind some users did not report it but simply reverted the
> patch (I know one guy who did that at least, there may well be more).
> Also, it's not been that long since the debugger patch landed.
I can also say the extra stuff in the backt
On Tue, 2004-06-15 at 21:07 +0200, Eric Pouech wrote:
> If I assume that any decent user should
> report this type of error, I only counted 2 reports (yours, and Shachar
> on some other topics), which is IMO a rather low figure.
> I'll adapt my time on winedbg hacking depending on this.
OK, bear
Mike Hearn a écrit :
Hi Eric,
I get a lot of messages like this since the new debugger shuffle patch
landed:
fixme:dbghelp:elf_new_wine_thunks Duplicate in kernel32:
audiocdW.6<40515de8-0012> audiocdW<40515de8->
For now I just changed the fixme to a warn in my local tree - what does
thi
Hi Eric,
I get a lot of messages like this since the new debugger shuffle patch
landed:
fixme:dbghelp:elf_new_wine_thunks Duplicate in kernel32:
audiocdW.6<40515de8-0012> audiocdW<40515de8->
For now I just changed the fixme to a warn in my local tree - what does
this message mean tho