Unimplemented function?

[Luis Carlos Busquets Pérez]

It seems that there is a regression in wine 1.3.28. Before bi-secting, I 
woul dlike to understand how that can happen. Apparently PlaChessV5.exe 
crashes due to:

wine: Call from 0x68215ca8 to unimplemented function 
msvcrt.dll._snwprintf_s, aborting

but when I look at the spec file, the function is defined:

@ varargs _snwprintf_s(ptr long long wstr) MSVCRT__snwprintf_s

and it exists in wcs.c

How is it that them it results as undefined?

Luis

[Maarten Lankhorst]

Hey,

On 09/18/2011 12:52 PM, Luis Carlos Busquets Pérez wrote:
> It seems that there is a regression in wine 1.3.28. Before bi-secting, I woul dlike to understand how that can happen. Apparently PlaChessV5.exe crashes due to:
>
> wine: Call from 0x68215ca8 to unimplemented function msvcrt.dll._snwprintf_s, aborting
>
> but when I look at the spec file, the function is defined:
>
> @ varargs _snwprintf_s(ptr long long wstr) MSVCRT__snwprintf_s
>
> and it exists in wcs.c
>
> How is it that them it results as undefined?

Are you using a native msvcrt dll?

~Maarten

[Luis Carlos Busquets Pérez]

Thanks Maarten. Your tip solved the issue. I wonder in any case if this 
should make rethink wine strategy and instead of forwarding funcs to a 
MS-name dll, depending on the API wine dlls could b e created. e.g.
msvcrt.dll, msvr71.dll, msvcr80.dll, msvcr90.dll, ... --> winecr

Other APIs could also be considered such as the long spoken d3dx:
d3dx9_36.dll, d3dx9_37.dll, d3dx9_38.dll ...d3dx10_43.dll, d3dx10_44.dll 
... --> wined3dx
msvcp... --> winecp
msxml2.dll, msxml3.dll, msxml4.dll ... --> winexml

Luis