Re: [patch] new command: 'dump' a region of memory in ascii and hex

[Stephane Carrez <Stephane dot Carrez at france dot sun dot com>]

Hi,
> 
> Here is a new function that I have found useful, maybe you will too.  The only
> thing I don't completely like about it is that I have to make my xterm wider
> than 80 chars for most of the output to look good.  This means it won't look
> very good at all at console.  Since the length of symbol names vary I'm not
> sure what can be done about this.  I think dynamically changing the number of
> chars per line would be confusing. 
> 

Looks interesting... 

What about merging your command in the existing examine command?

What about dumping the symbol info as a separate line, before the first
line and each time the symbol changes?

Something like:

<internal_error+3>:
0x683d3:     8d450c50 ff7508e8 05ffffff 9028756e    .E.P.u.......(un
0x683e3:     646f6375 6d656e74 65642065 72726e6f    documented.errno
0x683f3:     20256429 005589e5 538b5d08 53e84f7d    .%d).U..S.].S.O}
<safe_strerror+11>:
0x68403:      0c0083c4 0485c075 155368e0 83060068    .......u.Sh....h


Note that 'print_address' will generate lines that are even larger if
you "set print symbol-filename "

I think this is a general issue in Gdb that some outputs are really large
(specially when you debug with the sources).

	Stephane

-	-	-	-	-	-	-	-	-	-
Stephane |Sun Microsystems			|
 Carrez	 |Network Service Provider Division	| http://www.sun.com
	 |6 avenue Gustave Eiffel		|
	 |F-78182, St-Quentin-en-Yvelines-Cedex |

email: Stephane.Carrez@France.Sun.COM