-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
Figure out how to get errors reliably from r2.cmd(j) #28
Comments
Ok did some thoughs about this long standing issue and finally implemented r2pipe2 in r2. Check the new { command which takes cmd as a json object and returns a json with the output, error code , return value and log messages associated. The next step will be to try every single command (about 8000) and ensure the return code and errors are consistent with what’s expected. Which is not good it is right now but it was about the time to tackle this |
Amazing! This looks great so far!!
|
should bef ixed in radareorg/radare2#22975 . thanks for reporting! |
works great with that patch! |
Yeah better fill the r2 tickets in the r2 repo :) |
We talked briefly about this here
Unfortunately, option 2 has a few pitfalls:
axt @ jksdhfdskjf 2>foo
printsERROR: Invalid command 'axt @ klasjdlkasjd' (0x61)
but not in the foo fileOption 1 only works in some of the r2langs
Can you help me understand this issue and why it'd be hard to do it for, say r2lang-python? It's a pretty big issue for auto-mode.
The text was updated successfully, but these errors were encountered: