Skip to content
This repository has been archived by the owner on Apr 28, 2023. It is now read-only.

Add HackCon example #87

Merged
merged 2 commits into from
Sep 9, 2016
Merged

Add HackCon example #87

merged 2 commits into from
Sep 9, 2016

Conversation

P1kachu
Copy link
Contributor

@P1kachu P1kachu commented Sep 2, 2016

New example of CTF solved with angr

Signed-off-by: Stanislas P1kachu Lejay p1kachu@lse.epita.fr

Signed-off-by: Stanislas P1kachu Lejay <p1kachu@lse.epita.fr>
Signed-off-by: Stanislas P1kachu Lejay <p1kachu@lse.epita.fr>
@Manouchehri
Copy link
Contributor

Dang, that runtime is higher than I expected. Did threading make much of a difference?

Seems like a good example to profile.

@P1kachu
Copy link
Contributor Author

P1kachu commented Sep 3, 2016

Threading does something, but not that much. I am having a hard time profiling anything since I haven't enough RAM to run anything else sadly :/

@P1kachu
Copy link
Contributor Author

P1kachu commented Sep 3, 2016

But from my first experiment, I remember that stopping the analysis when entering the YAYY block rather than waiting for the message to be printed helped a lot, like 10 minutes faster 0.0
But maybe it was just some luck.

@ltfish
Copy link
Member

ltfish commented Sep 8, 2016

This one is really slow. I'm interested to know what is the fundamental reason that makes it that slow. Does it take a lot of time in solving? If that's the case, our upcoming support for incremental solving might help a lot.

I'm down to accept this PR, but it will not be tested in our CI (since it is too slow). I'll merge it in if I don't see any objection within the next 24 hours.

@zardus
Copy link
Member

zardus commented Sep 8, 2016

+1 to merge

On Sep 7, 2016 5:37 PM, "Fish" notifications@github.com wrote:

This one is really slow. I'm interested to know what was the fundamental
reason that makes it that slow. Does it take a lot of time in solving? If
that's the case, our upcoming support for incremental solving might help a
lot.

I'm down to accept this PR, but it will not be tested in our CI (since it
is too slow). I'll merge it in if I don't see any objection within the next
24 hours.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#87 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADSzlwGbq7dQ_At6QleS7FNJmJGZZFiaks5qn1jJgaJpZM4JzzyV
.

@ltfish ltfish merged commit f39e485 into angr:master Sep 9, 2016
@ltfish
Copy link
Member

ltfish commented Sep 9, 2016

Thanks man!

@P1kachu
Copy link
Contributor Author

P1kachu commented Sep 9, 2016

No problem! :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants