[patch] objdump dump fix

[Svein E. Seldal]

Hello,

objdump -s does not properly print objectfiles that have opb!=1. These 
includes the coff targets tic4x and tic54x (and probably a lot more 
targets). (These targets does not know about bytes, only increments in 
addresses - which span a storage- & bus-width of 16 or 32 bits.) Objdump 
loses information because it prints 16 bytes of data on one line (which 
is correct), and then increments the address pointer by 16 for the next 
line (which is incorrect).

The attached diff, is a suggestion to fix this problem.


Svein


binutils/ChangeLog:
2002-10-20  Svein E. Seldal  <Svein.Seldal@solidas.com>

	* objdump.c (dump_data): dump_data now adheres to
	  the opb value and dumps the data contents
	  properly for non-byte based object files.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: objdump.diff
URL: <https://sourceware.org/pipermail/binutils/attachments/20021020/a1f63885/attachment.ksh>