Debugging

[Ann and Jason Edmeades]

2 questions...

1. Is there any macro to dump out a hex dump of memory, eg.
TRACE_DUMP("Memory", pMem, numBytes);
If not, can I add one (inline in debug.h?)

2. When debugging using winedbg, is there any way to view the contents of a
lot of memory in one go (eg. hex dump of 256 bytes)?

Jason

[Dimitrie O. Paun]

On Thu, 24 Apr 2003, Ann and Jason Edmeades wrote:
> 2 questions...
>
> 1. Is there any macro to dump out a hex dump of memory, eg.
> TRACE_DUMP("Memory", pMem, numBytes);
> If not, can I add one (inline in debug.h?)

In general, I don't think it's such a good idea to just dump
memory. Most of the time the data is typed, so outputing
something more meaningful is better. We haven't had a need
for such a macro, so I would suspect it's something very
specific -- defining it locally would be better for now IMO.

-- 
Dimi.

[Mike Hearn]

> In general, I don't think it's such a good idea to just dump
> memory. Most of the time the data is typed, so outputing
> something more meaningful is better. We haven't had a need
> for such a macro, so I would suspect it's something very
> specific -- defining it locally would be better for now IMO.

Not to mention that such a dump might interfere with the terminal. I've
had Wine stomp all over my xterms enough by accident thanks :)

[Ann and Jason Edmeades]

> In general, I don't think it's such a good idea to just dump
> memory. Most of the time the data is typed, so outputing
> something more meaningful is better.

Well, my main reason was while debugging its useful to dump storage to see
what is going on, not so much to dump anything on a regular basis in trace.
Sometimes its useful to dump structures etc esp if corruption is occuring,
and a pre-supplied macro would have been very useful. I was just suprised
I couldnt find anything which actually did it already!
> Not to mention that such a dump might interfere with the terminal.
> I dont understand this? Any dump would go as tracepoints, formatted to
> only print out hex and printable characters, and nowhere near the screen.

Anyway, I'll put it in a local private header and noone will ever need see
it - Should keep everyone happy.

Regards,
Jason

[Eric Pouech]

> 2. When debugging using winedbg, is there any way to view the contents of a
> lot of memory in one go (eg. hex dump of 256 bytes)?

for chars
x /256c <addr>
or
x /256x <addr>
for bytes

A+

-- 
Eric Pouech