This commit is contained in:
gferg 2000-07-11 14:14:43 +00:00
parent 0f06b316c8
commit fb94c64b09
3 changed files with 43 additions and 10 deletions

View File

@ -16,8 +16,8 @@
<revhistory>
<revision>
<revnumber>v4.22</revnumber>
<date>July 7, 2000</date>
<revnumber>v4.23</revnumber>
<date>July 10, 2000</date>
<authorinitials>vv</authorinitials>
<revremark>
Addition of Liwest
@ -2674,6 +2674,11 @@ more or less fixed now; I am content with the Service.
Transfers go up to ~30k (intercontinental, too).
</para>
<para>
Please contact Bernd if you have additional questions. He has kindly
agreed to provide assistance to any current or new Linux user.
</para>
</sect2>
</sect1>

View File

@ -78,7 +78,7 @@ A brief overview of existing Alpha CPUs, chipsets and systems. </Para>
Assembly-HOWTO</ULink>,
<CiteTitle>Linux Assembly HOWTO</CiteTitle>
</Para><Para>
<CiteTitle>Updated: June 2000</CiteTitle>.
<CiteTitle>Updated: July 2000</CiteTitle>.
How to program in assembly language using FREE programming tools,
focusing on development for or from the Linux Operating System on
IA-32 (i386) platform. </Para>

View File

@ -16,7 +16,7 @@
<url url="mailto:konst@linuxassembly.org" name="Konstantin Boldyshev"> and
<url url="mailto:fare@tunes.org" name="Francois-Rene Rideau">
<date>v0.5j, June 14, 2000
<date>v0.5k, July 11, 2000
<abstract>
This is the Linux Assembly HOWTO.
@ -32,7 +32,7 @@ Contributions about them are gladly accepted.
<bf/Keywords/:
<tt/assembly, assembler, asm, inline asm, macroprocessor, preprocessor,
32-bit, IA-32, i386, x86, gas, as86, nasm, OS, kernel, system, libc,
32-bit, IA-32, i386, x86, nasm, gas, as86, OS, kernel, system, libc,
system call, interrupt, small, fast, embedded, hardware, port/
</abstract>
@ -161,6 +161,9 @@ I would like to thank following persons, by order of appearance:
Each version includes a few fixes and minor corrections,
that need not to be repeatedly mentioned every time.
<descrip>
<tag/Version 0.5k 11 Jul 2000/
Few additions to FAQ
<tag/Version 0.5j 14 Jun 2000/
Complete rearrangement of INTRODUCTION and RESOURCES;
FAQ added to RESOURCES, misc cleanups and additions
@ -881,7 +884,7 @@ distributions' contrib.
At the time of writing current version of NASM is 0.98.
Note: there's also an extented NASM version available at
Note: there's also an extended NASM version available at
<url url="ftp://ftp.linuxgames.com/crystal/nasm/">
know as 0.98e. It introduces several serious bugfixes and improvements,
so you may want to use it instead of "official" version.
@ -1857,7 +1860,7 @@ Hey, try to run it... Works? That's it. Pretty simple.
You main resource for Linux/UNIX assembly programming material
is <bf><url url="http://linuxassembly.org/resources.html"
name="Linux Assembly resources page"></bf>
name="Linux Assembly resources page"></bf>.
Do visit it, and get plenty of pointers to assembly projects,
tools, tutorials, documentation, guides, etc,
concerning different UNIX operating systems and CPUs.
@ -1899,7 +1902,7 @@ To subscribe send a blank message to <url url="mailto:linux-assembly@egroups.com
List archives are available at <url url="http://www.egroups.com/list/linux-assembly/">.
<sect1>Frequently asked questions (with asnwers)<label id="faq">
<sect1>Frequently asked questions (with answers)<label id="faq">
<p>
Here are frequently asked questions. Answers are taken
from the <ref id="res-list" name="linux-assembly mailing list">.
@ -1961,7 +1964,16 @@ and get it working. After that, the sky's the limit.
<sect2>How do I debug pure assembly code under Linux?
<p>
An answer from <url url="mailto:dl@gazeta.ru" name="Dmitry Bakhvalov">:
If you're using <tt/gas/, you should consult
<url url="http://www.cs.pdx.edu/~bjorn/CS200/linux_tutorial/"
name="Linux assembly Tutorial"> by Bjorn Chambless.
With <tt/nasm/ situation is a bit different, since it doesnot
support gdb specific debugging extensions.
Although <tt/gdb/ is source-level debugger, it can be used to debug
pure assembly code, and with some trickery you can make <tt/gdb/ to do what you need.
Here's an answer from <url url="mailto:dl@gazeta.ru" name="Dmitry Bakhvalov">:
<verb>
Personally, I use gdb for debugging asmutils. Try this:
@ -1991,10 +2003,26 @@ Personally, I use gdb for debugging asmutils. Try this:
Hope this helps.
</verb>
An additional note from ???:
<verb>
I have such a macro in my .gdbinit for quite some time now, and it
for sure makes life easier. A small difference : I use "x /8i $pc",
which guarantee a fixed number of disassembled instructions. Then,
with a well chosen size for my xterm, gdb output looks like it is
refreshed, and not scrolling.
</verb>
If you want to set breakpoints across your code, you can just use
<tt/int 3/ instruction as breakpoint (instead of entering address
manually in <tt/gdb/).
<sect2>Any other useful debugging tools?
<p>
Definitely <tt/strace/ can help a lot (<tt/ktrace/ and <tt/kdump/ on FreeBSD),
it is used to trace system calls and signals. Read <tt/man strace/ for details.
it is used to trace system calls and signals.
Read its manual page (<tt/man strace/) and <tt/strace --help/ output for details.
<sect2>How do I access BIOS functions from Linux (BSD, BeOS, etc)?
<p>