More DLL spec forwarding issues

[Shachar Shemesh]

Hi,

I got no reponse for the previous issue I posted (where placing forwards 
in a spec file did not perform as expected). I have tried to create 
actual functions that perform the forwards.

This works great when I use my own program. However, whem I try to use 
another program, it tries to call "GetProcAddress". Unfortunetly, there 
is no way to reimplement GetProcAddress in Wine, as the .spec.c file 
generated needs that function! This is a very problematic thing for me.

I tried forwarding GetProcAddress to GetProcAddress_unicows, but that 
did not help either. I get linker error (function redefined).

Please, can anyone help?

Shachar

[Alexandre Julliard]

Shachar Shemesh  writes:
> I got no reponse for the previous issue I posted (where placing
> forwards in a spec file did not perform as expected). I have tried to
> create actual functions that perform the forwards.

You shouldn't have to do that, the forwards should work. If they don't
you should debug it and find out why, that's not normal.

[Shachar Shemesh]

Alexandre Julliard wrote:
> Shachar Shemesh  writes:
> > I got no reponse for the previous issue I posted (where placing
> > forwards in a spec file did not perform as expected). I have tried to
> > create actual functions that perform the forwards.
>
> You shouldn't have to do that, the forwards should work. If they don't
> you should debug it and find out why, that's not normal.

The problem with that is that forwards do not show on +relay logs. I'm 
not sure why. This makes it almost impossible for me to check what went 
wrong.

The current solution started as a debugging aid, and then I found out 
that it (unlike the forwarding one) actually works.

Shachar

[Alexandre Julliard]

Shachar Shemesh  writes:
> The problem with that is that forwards do not show on +relay logs. I'm
> not sure why. This makes it almost impossible for me to check what
> went wrong.

The target function will show up in the relay trace; the forward is
just an alias, so you won't see unicows.LoadStringW in the trace but
you should see user32.LoadStringW.