4

I am: working with an Android game, using an Android Emulator, and trying to attach an android .so library to a process.

I have the whole IDA server set up, I can attach to processes when a classes.dex is loaded into IDA but, when I load the .so file and try to attach I get this message from IDA "The debugger could not attach to the selected process. This can perhaps indicate the process was terminated, or you don't have the necessary privileges." I see a problem with this because I have full root permission and I know for sure the process was not terminated. I read here that I may have to recompile the entire android kernel, Don't get me wrong I love wasting hours compiling but, I was just wondering if you guys can help me find something to solve this pesky little situation of mine.

Edit: This may be a dup but the dup wasn't answered and was from 2014. :/

Improve this question
1
  • Could you share / explain what the so is doing? – NirIzr Aug 26 '18 at 21:22
0

If

cat /proc/kmsg | grep "Restricted"

returns results that are similar to ones in the blog you linked, then indeed CONFIG_SEC_RESTRICT_FORK is set and the only way to get rid of it is to recompile the kernel

Improve this answer
1
  • I used the command both in ADBs shell and a Terminal emulator app and neither of them returned anything. This is really strange, that's why I asked you guys. Are there any other confounding variables that may be effecting this? – Frenchy Fry Nov 5 '16 at 19:23

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.