log_hexdump

Format and log a traditional memory dump starting at the address supplied and the length supplied. Use the supplied context string at the top and bottom to make it easy to identify. Use the internal logger-> debug function to write it to the current log file.

A typical dump file (with the date, time, and thread values removed) looks like the following:

DEBUG rap4 - =====      DSHTable in Loader:Run New Work    ========                  
DEBUG rap4 - 26583E0 >B0236800 00000000 C0C16502 00000000< .#h.......e..... 00000000 
DEBUG rap4 - 26583F0 >36000700 00000000 90846502 00000000< 6.........e..... 00000010 
DEBUG rap4 - 2658400 >58886702 00000000 F8C86E00 00000000< X.g.......n..... 00000020 
DEBUG rap4 - 2658410 >F07E6502 00000000 707F6502 00000000< .~e.....p.e..... 00000030 
DEBUG rap4 - 2658420 >687E6502 00000000<                   h~e.....         00000040 
DEBUG rap4 - =====      DSHTable in Loader:Run New Work    ======== 

Syntax

log_hexdump (char * contextString, void * address, long length)

Parameters

contextString

The string printed at the beginning and end of the trace segment for identification.

address

The beginning of the memory to dump.

length

The number of bytes to log.

Returns

uint16_t error_code (an error code) or ERR_NONE (value 0).


Created March 26, 2009. Send feedback on this help topic to Sybase Technical Publications: pubs@sybase.com