Detour, "Inline" asm. Access Violation. C++ to Delphi translation

This one is driving me bananas as it works in C++ and not in Delphi when to my eyes everything is the same. It's probably the way C++ handles variables from classes.

Anyway this is a small section for what I have:

  If Not(bNoRegs) Then
    begin
    Buffer.BufferAdd(Byte($89));
    Buffer.BufferAdd(Byte($0D));
    Buffer.BufferAdd(DWORD(@pClassInstance));
  end;

This is what it is in c++:

      if(!m_bNoRegs)
      {
            Buffer += (BYTE)0x89; //mov dword ptr, ecx
            Buffer += (BYTE)0x0D;
            Buffer += (DWORD)&m_pClassInstance;
      }

The Buffer variable isn't the issue as when the asm is written from the buffer it comes out right.
Now when each class is made the pClassInstance is set to nil(NULL in c++) it is a Pointer(BYTE * in c++). Now what is supposed to happen is pClassInstance is supposed to be set to ECX.
I.E. If ECX is $5E0000 pointer then pClassInstance should be equal to that. The same thing as doing pClassInstance := Pointer($5E0000);.

Now when this is executed on the delphi side I get an AV about not being able to access it.

Any ideas? If you need any other parts of the code just ask.
LVL 13
Dagan HooverDeveloperAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

itsmeandnobodyelseCommented:
I don't know Delphi but in C/C++

 (DWORD)&m_pClassInstance;

means

that the address of the pointer variable was pushed to the buffer and not the address the pointer was pointing to. That normally is a way to specify an output argument cause the callee might change the pointer value that way and the caller will get the new address assigned to m_pClassInstance.

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Dagan HooverDeveloperAuthor Commented:
"Yeh thats what I assumed it was. MOV DWORD PTR DS:[&m_pClassInstance] essentially dereferences the pointer. Since pClassInstance is pointing to nothing it's value is 0. When I debugged the program and stepped through the asm it was indeed the pointer to the variable and not what the pointer was pointing to. I still don't understand why the"

That was as far as I got in my reply until I realized why the variable couldn't be accessed. The code section:
           
            Buffer += (BYTE)0x89; //mov dword ptr, ecx
            Buffer += (BYTE)0x0D;
            Buffer += (DWORD)&m_pClassInstance;

It never got EXECUTE privileges!  Thanks to you confirming what I did was right it dawned on me! Thanks.
 
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Delphi

From novice to tech pro — start learning today.