Subject: Objdump stupidity
From: [email-masked] (Jon Thackray)

24 Oct 1997 07:20:02 -0700
Message-ID: <[email-masked]>
Reply-To: [email-masked]
To: [email-masked]

Why does objdump engage in the following stupid behaviour when
disassembling? For some reason, it's decided to continue disassembly
from the middle of an opcode, which has forced it to produce the '%?'

100015f1 <.lf>:
     0:	bb a0 81 00 10 	movl   $0x100081a0,%ebx
     5:	ff 53 04       	call   *0x4(%ebx)
     8:	89 45 f8       	movl   %eax,0xfffffff8(%ebp)
     b:	ff 75 f8       	pushl  0xfffffff8(%ebp)
     e:	8b 05 8c b3 00 	movl   0x1000b38c,%eax
    13:	10 

10001601 <.lf>:
     0:	8c b3 00 10 b9 	movw   %?,0x2b91000(%ebx)
     5:	02 
     6:	00 00          	addb   %al,(%eax)
     8:	00 8b 1d 8c b4 	addb   %cl,0xb48c1d(%ebx)

-
For help on using this list (especially unsubscribing), send a message to
"[email-masked]" with one line of text: "help".