I am now trying to debug the exact parameters D3DXCreateBox uses in its call to D3DXCreateMesh to create its mesh.
I would like to run make test with a native DLL.
I have tried both: * using winecfg to set native overrides * WINEDLLOVERRIDES="d3dx9_36=n" make test
but neither seems to do the trick.
Any hints appreciated.
Thank you Misha
On Tue, Jul 6, 2010 at 3:29 PM, Misha Koshelev misha680@gmail.com wrote:
I am now trying to debug the exact parameters D3DXCreateBox uses in its call to D3DXCreateMesh to create its mesh.
I would like to run make test with a native DLL.
I have tried both:
- using winecfg to set native overrides
- WINEDLLOVERRIDES="d3dx9_36=n" make test
but neither seems to do the trick.
Any hints appreciated.
try: ../../../wine d3dx9_36_test.exe.so mesh
On Tue, Jul 6, 2010 at 3:39 PM, Austin English austinenglish@gmail.com wrote:
On Tue, Jul 6, 2010 at 3:29 PM, Misha Koshelev misha680@gmail.com wrote:
I am now trying to debug the exact parameters D3DXCreateBox uses in its call to D3DXCreateMesh to create its mesh.
I would like to run make test with a native DLL.
I have tried both:
- using winecfg to set native overrides
- WINEDLLOVERRIDES="d3dx9_36=n" make test
but neither seems to do the trick.
Any hints appreciated.
try: ../../../wine d3dx9_36_test.exe.so mesh
I should have clarified, you shouldn't be looking at native dll internals, of course (' trying to debug the exact parameters D3DXCreateBox uses in its call to D3DXCreateMesh to create its mesh.'). Only use MSDN or black box testing with conformance tests to verify native behavior.
Also see http://wiki.winehq.org/DeveloperFaq#head-fed5011434f62ae1a88baebfb8193a37ea7...
Oops good thing I did not yet figure out how to use a native d3dx9_36 then so no compromise of my ability to contribute.
Just to clarify then... I may NOT use wine to monitor calls within a native DLL? Specifically, I may not determine what parameters one native function passes to another?
Thank you Misha
On Jul 6, 2010 4:10 PM, "Austin English" austinenglish@gmail.com wrote:
On Tue, Jul 6, 2010 at 3:39 PM, Austin English austinenglish@gmail.com wrote:
On Tue, Jul 6, 201...
I should have clarified, you shouldn't be looking at native dll internals, of course (' trying to debug the exact parameters
D3DXCreateBox uses in its call to D3DXCreateMesh to create its mesh.'). Only use MSDN or black box testing with conformance tests to verify native behavior.
Also see http://wiki.winehq.org/DeveloperFaq#head-fed5011434f62ae1a88baebfb8193a37ea7...
-- -Austin
2010/7/6 Misha Koshelev misha680@gmail.com:
Oops good thing I did not yet figure out how to use a native d3dx9_36 then so no compromise of my ability to contribute.
Just to clarify then... I may NOT use wine to monitor calls within a native DLL? Specifically, I may not determine what parameters one native function passes to another?
Correct, you can't check what happens inside native dlls nor the communication between two native functions or components. What you can do is to test the behavior of a native function as a black box, i.e. give it some inputs and see what it outputs. Sorry if I inadvertently put you on the wrong path...
Matteo.
On Wed, 2010-07-07 at 00:17 +0200, Matteo Bruni wrote:
2010/7/6 Misha Koshelev misha680@gmail.com:
Oops good thing I did not yet figure out how to use a native d3dx9_36 then so no compromise of my ability to contribute.
Just to clarify then... I may NOT use wine to monitor calls within a native DLL? Specifically, I may not determine what parameters one native function passes to another?
Correct, you can't check what happens inside native dlls nor the communication between two native functions or components. What you can do is to test the behavior of a native function as a black box, i.e. give it some inputs and see what it outputs. Sorry if I inadvertently put you on the wrong path...
Matteo.
No worries. Good to know. Thank you.
Misha
-
Austin English -
Matteo Bruni -
Misha Koshelev