"Fossies" - the Fresh Open Source Software Archive

Member "nasm-2.15.05/doc/html/nasmdoce.html" (28 Aug 2020, 6249 Bytes) of package /linux/misc/nasm-2.15.05-xdoc.tar.xz:


As a special service "Fossies" has tried to format the requested source page into HTML format using (guessed) HTML source code syntax highlighting (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file.

    1 <?xml version="1.0" encoding="UTF-8" standalone="no" ?>
    2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
    3 <html xmlns="http://www.w3.org/1999/xhtml">
    4 <head>
    5 <title>NASM - The Netwide Assembler</title>
    6 <link href="nasmdoc.css" rel="stylesheet" type="text/css" />
    7 <link href="local.css" rel="stylesheet" type="text/css" />
    8 </head>
    9 <body>
   10 <ul class="navbar">
   11 <li class="first"><a class="prev" href="nasmdocd.html">Appendix D</a></li>
   12 <li><a class="toc" href="nasmdoc0.html">Contents</a></li>
   13 <li class="last"><a class="index" href="nasmdoci.html">Index</a></li>
   14 </ul>
   15 <div class="title">
   16 <h1>NASM - The Netwide Assembler</h1>
   17 <span class="subtitle">version 2.15.05</span>
   18 </div>
   19 <div class="contents"
   20 >
   21 <h2 id="appendix-E">Appendix E: Contact Information</h2>
   22 <h3 id="section-E.1">E.1 Website</h3>
   23 <p>NASM has a website at
   24 <a href="http://www.nasm.us/"><code>http://www.nasm.us/</code></a>.</p>
   25 <p>New releases, release candidates, and daily development snapshots of
   26 NASM are available from the official web site in source form as well as
   27 binaries for a number of common platforms.</p>
   28 <h4 id="section-E.1.1">E.1.1 User Forums</h4>
   29 <p>Users of NASM may find the Forums on the website useful. These are,
   30 however, not frequented much by the developers of NASM, so they are not
   31 suitable for reporting bugs.</p>
   32 <h4 id="section-E.1.2">E.1.2 Development Community</h4>
   33 <p>The development of NASM is coordinated primarily though the
   34 <code>nasm-devel</code> mailing list. If you wish to participate in
   35 development of NASM, please join this mailing list. Subscription links and
   36 archives of past posts are available on the website.</p>
   37 <h3 id="section-E.2">E.2 Reporting Bugs</h3>
   38 <p>To report bugs in NASM, please use the bug tracker at
   39 <a href="http://www.nasm.us/"><code>http://www.nasm.us/</code></a> (click
   40 on "Bug Tracker"), or if that fails then through one of the contacts in
   41 <a href="#section-E.1">section E.1</a>.</p>
   42 <p>Please read <a href="nasmdoc2.html#section-2.2">section 2.2</a> first,
   43 and don't report the bug if it's listed in there as a deliberate feature.
   44 (If you think the feature is badly thought out, feel free to send us
   45 reasons why you think it should be changed, but don't just send us mail
   46 saying `This is a bug' if the documentation says we did it on purpose.)
   47 Then read <a href="nasmdo13.html#section-13.1">section 13.1</a>, and don't
   48 bother reporting the bug if it's listed there.</p>
   49 <p>If you do report a bug, <em>please</em> make sure your bug report
   50 includes the following information:</p>
   51 <ul>
   52 <li>
   53 <p>What operating system you're running NASM under. Linux, FreeBSD, NetBSD,
   54 MacOS X, Win16, Win32, Win64, MS-DOS, OS/2, VMS, whatever.</p>
   55 </li>
   56 <li>
   57 <p>If you compiled your own executable from a source archive, compiled your
   58 own executable from <code>git</code>, used the standard distribution
   59 binaries from the website, or got an executable from somewhere else (e.g. a
   60 Linux distribution.) If you were using a locally built executable, try to
   61 reproduce the problem using one of the standard binaries, as this will make
   62 it easier for us to reproduce your problem prior to fixing it.</p>
   63 </li>
   64 <li>
   65 <p>Which version of NASM you're using, and exactly how you invoked it. Give
   66 us the precise command line, and the contents of the <code>NASMENV</code>
   67 environment variable if any.</p>
   68 </li>
   69 <li>
   70 <p>Which versions of any supplementary programs you're using, and how you
   71 invoked them. If the problem only becomes visible at link time, tell us
   72 what linker you're using, what version of it you've got, and the exact
   73 linker command line. If the problem involves linking against object files
   74 generated by a compiler, tell us what compiler, what version, and what
   75 command line or options you used. (If you're compiling in an IDE, please
   76 try to reproduce the problem with the command-line version of the
   77 compiler.)</p>
   78 </li>
   79 <li>
   80 <p>If at all possible, send us a NASM source file which exhibits the
   81 problem. If this causes copyright problems (e.g. you can only reproduce the
   82 bug in restricted-distribution code) then bear in mind the following two
   83 points: firstly, we guarantee that any source code sent to us for the
   84 purposes of debugging NASM will be used <em>only</em> for the purposes of
   85 debugging NASM, and that we will delete all our copies of it as soon as we
   86 have found and fixed the bug or bugs in question; and secondly, we would
   87 prefer <em>not</em> to be mailed large chunks of code anyway. The smaller
   88 the file, the better. A three-line sample file that does nothing useful
   89 <em>except</em> demonstrate the problem is much easier to work with than a
   90 fully fledged ten-thousand-line program. (Of course, some errors
   91 <em>do</em> only crop up in large files, so this may not be possible.)</p>
   92 </li>
   93 <li>
   94 <p>A description of what the problem actually <em>is</em>. `It doesn't
   95 work' is <em>not</em> a helpful description! Please describe exactly what
   96 is happening that shouldn't be, or what isn't happening that should.
   97 Examples might be: `NASM generates an error message saying Line 3 for an
   98 error that's actually on Line 5'; `NASM generates an error message that I
   99 believe it shouldn't be generating at all'; `NASM fails to generate an
  100 error message that I believe it <em>should</em> be generating'; `the object
  101 file produced from this source code crashes my linker'; `the ninth byte of
  102 the output file is 66 and I think it should be 77 instead'.</p>
  103 </li>
  104 <li>
  105 <p>If you believe the output file from NASM to be faulty, send it to us.
  106 That allows us to determine whether our own copy of NASM generates the same
  107 file, or whether the problem is related to portability issues between our
  108 development platforms and yours. We can handle binary files mailed to us as
  109 MIME attachments, uuencoded, and even BinHex. Alternatively, we may be able
  110 to provide an FTP site you can upload the suspect files to; but mailing
  111 them is easier for us.</p>
  112 </li>
  113 <li>
  114 <p>Any other information or data files that might be helpful. If, for
  115 example, the problem involves NASM failing to generate an object file while
  116 TASM can generate an equivalent file without trouble, then send us
  117 <em>both</em> object files, so we can see what TASM is doing differently
  118 from us.</p>
  119 </li>
  120 </ul>
  121 </div>
  122 </body>
  123 </html>