Closed tyb0807 closed 6 years ago
Wouldn't this get wiped in the tracer merge anyways?
On Oct 6, 2017 5:27 PM, "tyb0807" notifications@github.com wrote:
@rhelmot https://github.com/rhelmot @salls https://github.com/salls please review this. Thanks!
You can view, comment on, or merge this pull request online at:
https://github.com/angr/tracer/pull/46 Commit Summary
- Rex needs this
File Changes
- M tracer/runner.py https://github.com/angr/tracer/pull/46/files#diff-0 (3)
- M tracer/tracer.py https://github.com/angr/tracer/pull/46/files#diff-1 (2)
Patch Links:
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/angr/tracer/pull/46, or mute the thread https://github.com/notifications/unsubscribe-auth/ADSzl-ARVlKBrguby5rndWasbd05IePmks5spjizgaJpZM4PwkEr .
Yes, but if you want to fix rex first (that's what I'm doing), you'll need to fix the old tracer with this.
So to confirm: you want to merge this, and rebase your tracer-merge PR on top of it?
Yup, otherwise you cannot verify rex fixes can you?
From my personal perspective, fixing rex with the current state is useful only to help make sure it works after the tracer merge. If you tell me it works, then we end up merging the tracer into angr and it still works, then that's good enough for me :-)
That being said, I'm down to merge this. @salls, can you sign off? I don't know this part enough to judge.
I see, so please feel free to close this. The most important thing now is fixing rex anyways, I need your help on that :(
Looks good to me
@rhelmot @salls please review this. Thanks!