You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there. Normally in arm64 if we assemble an instruction like "mov x0, x1" or "mov x0, #0x100". it would be easily done. But in my case, "mov x0, Varaible" , the second operand is not fixed, its value will change. So, when I use ks_asm(&ks, ???, ......., ...., .... ) this API, what string I should input for the second argument?
Below is an example of my code, as you can see, each loop will increase the value of ucRun. So the value of ucRun is definitely not fixed here. So, could you give me some useful advise so I can make it work?
Hi there. Normally in arm64 if we assemble an instruction like "mov x0, x1" or "mov x0, #0x100". it would be easily done. But in my case, "mov x0, Varaible" , the second operand is not fixed, its value will change. So, when I use ks_asm(&ks, ???, ......., ...., .... ) this API, what string I should input for the second argument?
Below is an example of my code, as you can see, each loop will increase the value of ucRun. So the value of ucRun is definitely not fixed here. So, could you give me some useful advise so I can make it work?
for(int i = 0; i < 10; ++i)
{
static size_t ucRun = 0x1000;
ucRun = ucRun + 0x100;
size_t ksAsmRet = ks_asm(ptrKS, "mov x9, ucRun", 0, &encodeBuf, &encodeSz, &encodeCount);
}
The text was updated successfully, but these errors were encountered: