ts of
Wine, notably ntdll and kernel32, but probably also others. Does
anyone know why? Is there a workaround, or a better method altogether?
The "Performance" page on the Wine Wiki suggests that it may be
possible to use Visual Studio's profiling tools. Can anyone offer any
tips for compiling and profiling WineD3D with Visual Studio?
-- graham
d the most significant causes
of the performance difference? Any tips for effective profiling or
tracing?
Thanks.
-- graham
ve it.)
* We no longer need to measure how long sched_yield made us wait, so
we can reorder the NtQuerySystemTime calls. The break condition is
unchanged, so the second NtQuerySystemTime call is often skipped.
> http://www.winehq.org/pipermail/wine-devel/2004-November/030796.html
Thanks, I will look at this.
-- graham
On 09/03/13 14:08, André Hentschel wrote:
> Am 09.03.2013 02:40, schrieb Graham:
>> On 08/03/13 22:40, Francois Gouget wrote:
>>> On Fri, 8 Mar 2013, Marcus Meissner wrote:
>>> [...]
>>>> "real NOVICE" and using LD_PRELOAD or "hotpatching&qu
On 09/03/13 06:03, Marcus Meissner wrote:
> On Sat, Mar 09, 2013 at 01:40:00AM +0000, Graham wrote:
>> On 08/03/13 22:40, Francois Gouget wrote:
>>> On Fri, 8 Mar 2013, Marcus Meissner wrote:
>>> [...]
>>>> "real NOVICE" and using LD_PRELOAD or
On 08/03/13 22:40, Francois Gouget wrote:
> On Fri, 8 Mar 2013, Marcus Meissner wrote:
> [...]
>> "real NOVICE" and using LD_PRELOAD or "hotpatching" does not fit together
>> for me...?
>>
>> - wine uses it own elfloader, which might cause issues.
> Really? I thought it used the standard elf loade
ancient wisdom isn't backed by tests there's a fair chance that
> it might not be applicable today. Or that it was a wrong theory
Interesting. Unfortunately, I have no idea how to go about writing
tests for this. Can anyone offer any suggestions?
-- graham
I use a LD_PRELOAD before running wine so that i can debug my application.
The library which is preloaded is able to replace system dlsym and from
that, other consequence library call.
There is no problem until, i put some Detour code(hot patching) into the
kernel32.dll.so address space. But the
correct, and my patch is garbage.
Lesson learned: consult history.
-- graham
