diff options
| author | KyleMiles <krm504@nyu.edu> | 2021-02-10 22:02:50 +0000 |
|---|---|---|
| committer | KyleMiles <krm504@nyu.edu> | 2021-03-17 23:43:59 +0000 |
| commit | 1515df8e71412787470b27d04ed9b2944fca0fdc (patch) | |
| tree | 400fbc792da7de1cc62e0fae171aae2bdf346869 /python/binaryview.py | |
| parent | 41e11f8387ebb3275da31994b85a7a8b6256eb99 (diff) | |
Misc typo changes, const changes, code cleanup, and example updates
Diffstat (limited to 'python/binaryview.py')
| -rw-r--r-- | python/binaryview.py | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/python/binaryview.py b/python/binaryview.py index 741c08a7..b1bbdb6e 100644 --- a/python/binaryview.py +++ b/python/binaryview.py @@ -253,6 +253,7 @@ class AnalysisCompletionEvent(object): def view(self, value): self._view = value + # This has no functional purposes; # we just need it to stop Python from prematurely freeing the object _binaryview_events = {} @@ -260,7 +261,7 @@ class BinaryViewEvent(object): """ The ``BinaryViewEvent`` object provides a mechanism for receiving callbacks when a BinaryView is Finalized or the initial analysis is finished. The BinaryView finalized callbacks run before the - intial analysis starts. The callbacks run one-after-another in the same order as they get registered. + initial analysis starts. The callbacks run one-after-another in the same order as they get registered. It is a good place to modify the BinaryView to add extra information to it. For newly opened binaries, the initial analysis completion callbacks run after the initial analysis, @@ -273,7 +274,7 @@ class BinaryViewEvent(object): :Example: >>> def callback(bv): - ... print('start: 0x%x' % bv.start) + ... print('start: 0x%x' % bv.start) ... >>> BinaryViewType.add_binaryview_finalized_event(callback) """ |
