diff options
author | H. Peter Anvin <hpa@linux.intel.com> | 2017-03-31 12:03:57 -0700 |
---|---|---|
committer | H. Peter Anvin <hpa@linux.intel.com> | 2017-03-31 12:03:57 -0700 |
commit | 17df43c8f277805d7571c9c5b6e4ea88326132eb (patch) | |
tree | c6d3cfc08796e50619e1ec70e94662fa76bafd62 /doc | |
parent | ac06133ed24c10137d43fe5bc3440dcc8cadd594 (diff) | |
download | nasm-17df43c8f277805d7571c9c5b6e4ea88326132eb.tar.gz |
outdbg: add %pragma for maximum size of a raw data dump
A raw data dump can potentially be very large, especially when
incbin is used. Allow a %pragma for setting the maximum dump
size (defaults to 128 bytes.)
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
Diffstat (limited to 'doc')
-rw-r--r-- | doc/nasmdoc.src | 14 |
1 files changed, 9 insertions, 5 deletions
diff --git a/doc/nasmdoc.src b/doc/nasmdoc.src index 2d84b64e..fd3c6b6f 100644 --- a/doc/nasmdoc.src +++ b/doc/nasmdoc.src @@ -6217,11 +6217,6 @@ a hint as to where to find requested symbols. \H{dbgfmt} \i\c{dbg}: Debugging Format -The \c{dbg} output format is not built into NASM in the default -configuration. If you are building your own NASM executable from the -sources, you can define \i\c{OF_DBG} in \c{output/outform.h} or on the -compiler command line, and obtain the \c{dbg} output format. - The \c{dbg} format does not output an object file as such; instead, it outputs a text file which contains a complete list of all the transactions between the main body of NASM and the output-format @@ -6262,6 +6257,15 @@ yourself (using \c{EXTERN}, for example) if you really need to get a \c{dbg} accepts any section name and any directives at all, and logs them all to its output file. +\c{dbg} accepts and logs any \c{%pragma}, but the specific +\c{%pragma}: + +\c %pragma dbg maxdump <size> + +where \c{<size>} is either a number or \c{unlimited}, can be used to +control the maximum size for dumping the full contents of a +\c{rawdata} output object. + \C{16bit} Writing 16-bit Code (DOS, Windows 3/3.1) |