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
I was wondering what is the correct way to use threading with unicorn. Currently, I’m working on a project emulating AArch64 on an x86 host. When threading, each thread gets its own unicorn instance and stack but with a shared code memory. Is this always safe? There haven’t been any issues with this approach so far, but I’m now testing on an RISC-V and there’s been emulation issues that appear exclusively when threading on RISC-V. (#2254)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I was wondering what is the correct way to use threading with unicorn. Currently, I’m working on a project emulating AArch64 on an x86 host. When threading, each thread gets its own unicorn instance and stack but with a shared code memory. Is this always safe? There haven’t been any issues with this approach so far, but I’m now testing on an RISC-V and there’s been emulation issues that appear exclusively when threading on RISC-V. (#2254)
Beta Was this translation helpful? Give feedback.
All reactions