Visualization of possible ways to interpret(disasm) bytestream

[j123123]

Can be done using html table. Something like this:

48	b8	01	48	31	c0	48	8d	04	18
movabsq $0x18048d48c0314801, %rax
	movl $0xc0314801, %eax					leaq (%rax, %rbx), %rax
			xorq %rax, %rax
				xorl %eax, %eax
		addl %ecx, 0x31(%rax)			rorb $4, -0x73(%rax)
							leal (%rax, %rbx), %eax
								addb $0x18, %al

[radare]

i would not go for visual mode this, imho:

• enhace the current pda= to support variable column width

and if you want the table mode it is better to just go for html and implement it in the webui

On 25 Jun 2016, at 11:57, szt <notifications@github.com mailto:notifications@github.com> wrote:

Current behaviour of pda is not very good to see specific instruction chain

$ echo -n -e '\x48\xb8\x01\x48\x31\xc0\x48\x8d\x04\x18' > test.bin $ radare2 test.bin -- I accidentally radared my filesystem today. [0x00000000]> pda 0x0-0xA 0x00000000 48b8014831c0488d0418 movabs rax, 0x18048d48c0314801 0x00000001 b8014831c0 mov eax, 0xc0314801 0x00000002 014831 add dword [rax + 0x31], ecx 0x00000003 4831c0 xor rax, rax 0x00000004 31c0 xor eax, eax 0x00000005 c0488d04 ror byte [rax - 0x73], 4 0x00000006 488d0418 lea rax, [rax + rbx] 0x00000007 8d0418 lea eax, [rax + rbx] 0x00000008 0418 add al, 0x18 0x00000009 ??? Need something like

0x00000000 48 b8 01 48 31 c0 48 8d 04 18 movabs rax, 0x18048d48c0314801 0x00000001 b8 01 48 31 c0 mov eax, 0xc0314801
0x00000002 01 48 31 add dword [rax + 0x31], ecx 0x00000003 48 31 c0 xor rax, rax 0x00000004 31 c0 xor eax, eax 0x00000005 c0 48 8d 04 ror byte [rax - 0x73], 4 0x00000006 48 8d 04 18 lea rax, [rax + rbx] 0x00000007 8d 04 18 lea eax, [rax + rbx] 0x00000008 04 18 add al, 0x18 or maybe something like this:

48 b8 01 48 31 c0 48 8d 04 18 movabsq $0x18048d48c0314801, %rax

movl $0xc0314801, %eax leaq (%rax, %rbx), %rax

xorq %rax, %rax

xorl %eax, %eax

addl %ecx, 0x31(%rax) rorb $4, -0x73(%rax)

leal (%rax, %rbx), %eax

addb $0x18, %al for visual mode: https://camo.githubusercontent.com/79b4b99054bdcb2360e602eae153b77cbe8463fa/687474703a2f2f64756d702e6269746368656573652e6e65742f66696c65732f77656a6173796c2f64726177696e672e737667 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/radare/radare2/issues/5211, or mute the thread https://github.com/notifications/unsubscribe/AA3-luKiQoWQtBzfzl-KqzBBcxkwJ_diks5qPPuHgaJpZM4I-T72.

[ret2libc]

This issue has been moved from radareorg/radare2 to radareorg/ideas as we are trying to clean our backlog and this issue has probably been created a long while ago. This is an effort to help contributors understand what are the actionable items they can work on, prioritize issues better and help users find active/duplicated issues more easily. If this is not an enhancement/improvement/general idea but a bug, feel free to ask for re-transfer to main repo. Thanks for your understanding and contribution with this issue.