From 1c49eb5989bda46e4a79eeaf8c05804ce7a8b599 Mon Sep 17 00:00:00 2001 From: rocky Date: Tue, 26 Apr 2022 18:09:16 -0400 Subject: [PATCH] Revise what pydisassemble is about --- uncompyle6/bin/pydisassemble.py | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/uncompyle6/bin/pydisassemble.py b/uncompyle6/bin/pydisassemble.py index 04048259..90ab5b26 100755 --- a/uncompyle6/bin/pydisassemble.py +++ b/uncompyle6/bin/pydisassemble.py @@ -1,7 +1,7 @@ #!/usr/bin/env python # Mode: -*- python -*- # -# Copyright (c) 2015-2016, 2018, 2020 by Rocky Bernstein +# Copyright (c) 2015-2016, 2018, 2020, 2022 by Rocky Bernstein # from __future__ import print_function import sys, os, getopt @@ -16,11 +16,18 @@ Usage: {0} [OPTIONS]... FILE {0} [--help | -h | -V | --version] -Disassemble FILE with the instruction mangling that is done to +Disassemble/Tokenize FILE with in the way that is done to assist uncompyle6 in parsing the instruction stream. For example instructions with variable-length arguments like CALL_FUNCTION and BUILD_LIST have argument counts appended to the instruction name, and -COME_FROM instructions are inserted into the instruction stream. +COME_FROM psuedo instructions are inserted into the instruction stream. +Bit flag values encoded in an operand are expanding, EXTENDED_ARG +value are folded into the following instruction operand. + +Like the parser, you may find this more high-level and or helpful. +However if you want a true disassembler see the Standard built-in +Python library moudle module "dis", or pydisasm from the cross-version +Python bytecode package "xdis". Examples: {0} foo.pyc