-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation fault opening main iaito window (M1 Mac, macOS 12) #67
Comments
Unfortunely, iaito is using a single core instance from multiple threads, which is conceptually wrong, so now, that r2 is thread safe, iaito fails hard by assuming globals are initialized and uses the mutexes incorrectly too. I pushed some fixes in r2 and iaito, but its still not yet fully working (but at least is not crashing). But you will need to build r2 without threads to try it out.
|
Thanks for the quick reply and I understand that as an open source project things might not always be working out right away. I actually just wanted to try iaito out, to see how different it is from command line r2 and got confused because I couldn't find an issue, so no worries |
So I was able to run it once, trying to open decompiler crashed it though (maybe r2ghidra?). Now when I try to open it again (make run or in /Applicatons) I get: rarun2 libpath=/usr/local/lib program=build/iaito.app/Contents/MacOS/iaito
QCommandLineParser: already having an option named "w"
make: *** [run] Killed: 9 Strange thing is when I run it via lldb it crashes but still opens. And decompiler doesn't crash, but it loads forever |
Did you git pull r2 and iaito and compiled r2 without threads? Otherwise if your purpose is to try it out i would recommend you to build r2-5.4 or 5.5 which didnt had thread safety magic yet |
Yeah I pulled latest master branch from both and build as per your instruction. But I can try tomorrow again (and use your suggestion)
|
Ignore the last edit after restarting it worked. With the master branch decompiler still doesn't work though, but version 5.5 was looking fine, thanks for your help! |
Same issue on Fedora Linux with the r2 5.6.0 release . |
Yep that's expected because Iaito is far from thread safe. I dont think i can cook the needed apis before 5.7. I will update and release a new iaito when this is ready. |
Seems that -Dwant_threads=false is gone from radare2 5.6.4 ... did anything change regarding compiling iaito with recent radare2 versions? |
Sorry - my fault - it is working with radare2 5.6.4 |
Is the disasm issue (only showing instruction without arguments) still happening? |
Yes unfortunately issue with not showing the arguments is still there. And BTW there are some comming issues with the recent update of kf5 from 5.90 to 5.91 kf5-syntax-highlighting-devel stopped advertising include dir /usr/include/KF5 |
The missing operands is fixed in master. What should we do to fix the kf5 issue? |
OK operands fixed in master. For #70 KF5 5.91 I am adding include for /usr/include/KF5 when compiling with syntax highlighting. Probably not a best solution, but works for now. |
I believe this incident can be closed - please @Maxung can you confirm for the MacOS side? |
Currently getting this, I'll try tomorrow on my other Mac to see if it's environment problem on my side:
|
Ok tested on a pretty fresh system (macOS 12.2) and building + running just fine. Only thing is that the decompiler (pdc) is still loading forever, but I think that might be a separate issue |
Environment Details
QCommandLineParser: already having an option named "w" iaito 5.5.0 Sun Feb 6 15:24:56 CET 2022 radare2 5.6.0 27361 @ darwin-arm-64 git.5.6.0 commit: e9e600a9a4c22a1e4aa901ab50e1d744648bd722 build: 2022-02-06__13:47:14 Darwin arm64
Description
Iaito crashes (seg fault) after pressing start on the file selection dialog. It doesn't matter if I select a file or check "don't open any file". Installed r2 from source successfully (and fully working).
Following was used to build iaito:
Following is the lldb output (with and without selected file):
The text was updated successfully, but these errors were encountered: