-
Notifications
You must be signed in to change notification settings - Fork 80
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
add CLI component #305
add CLI component #305
Conversation
…thods * add display_with methods to Function, BasicBlock, and Mnemonic for pp * add function filter to command line options * default disassemble and print every found function
the
|
Pretty cool. The I (now) agree that using a branch on the main repo is easier when working on something collaboratively. I forgot that you can't force push into somebody else branch (after rebase for example). |
cli/src/main.rs
Outdated
match filter { | ||
Some(filter) => { | ||
for function in pipe.wait() { | ||
info!("derp"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wat?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
testing if you're awake 🤣
cli/src/main.rs
Outdated
None | ||
} | ||
}).collect::<Vec<_>>(); | ||
// todo: sort by address |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about this?
So, sorting the functions has revealed that there still appear to be dup functions:
|
RE: ya, display with is a hack; I also wish I didn't have to pass in the whole |
Dunno what's up with that appveyor CI failure ? |
Just a hiccup. |
I made several changes based on your branch:
For assembly printing, I implemented a
display_with
function on an older branch that took the program as an argument and printed it very nicely, but it needed the display structs and display logic that was originally in the qt/qml portion; I think we should move those display structs into pipeline and have them be reusable, otherwise the cli will fork on important issues, and will make maintenance harder IMHO@flanfly what do you think?
--- META ---
Also, so I made this a branch on panopticon, can remove if you like, but I think we should consider this for development model; if your branch hadn't been from your own repo, I could in principle push commits to it directly (very nice for basic fixes, etc.), or make a PR merging commits into your branch; to do that against your own branch in your own repo is much harder, and not sure what the gain is.
anyway if you don't like having branch on panopticon, I can delete this and push to my master, but again, i strongly urge to consider other development model.