-
Notifications
You must be signed in to change notification settings - Fork 799
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
pdisas sets the disassembly-flavor to intel #100
Comments
peda sets |
@longld Actually you happen to support both syntaxes. For intance, # lib/utils.py, in function format_disasm_code
# line 526
addr, opcode = to_int(m.group(1)), m.group(2)
for c in colorcodes:
if c in opcode:
color = colorcodes[c]
if c == "call":
for f in VULN_FUNCTIONS:
if f in line.split(":\t", 1)[-1]:
style = "bold, underline"
color = "red"
break
break It so happens that both AT&T's (GAS) syntax and Intel's use the same opcodes mnemonics, at least at their core. Your "is a substring of" test means you maintain compatiblity regarding both syntaxes, which won't evolve in the future by the way. Ergo, you do support both syntaxes with your parsing, and should therefore not favour one syntax over another. The suggested fix, as said in my initial post, is to delete the line 777 from self.execute("set disassembly-flavor intel") # get rid of this line I have commented out this line in my code and haven't encountered any problem whatsoever. |
File 'peda.py', lines 759 and 777:
I, as many other users, prefer the GAS syntax. Other users may prefer the Intel syntax, and that's why there is a
set disassembly-flavor XXX
setting.I can't see a reason as to why
pdisas
, a supposedly improveddisas
, should blatantly ignore such a setting and impose either flavor.The text was updated successfully, but these errors were encountered: