os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Restore lost <replaceable> tags.

Browse source
This commit is contained in:
Warren Block 2014-04-28 20:13:07 +00:00
parent ff76bf5f73
commit 21115a05b8
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=44678
7 changed files with 48 additions and 48 deletions
Download patch file Download diff file Expand all files Collapse all files

18
en_US.ISO8859-1/books/developers-handbook/tools/chapter.xml
View file

@ -600,7 +600,7 @@
compiler to add it.</para>
<para>The rule is that if the library is called
<filename>libsomething.a</filename>,
<filename>lib<replaceable>something</replaceable>.a</filename>,
you give <command>cc</command> the argument
<option>-l<replaceable>something</replaceable></option>.
For example, the math library is
@ -996,7 +996,7 @@ free(foo);
<para>to find out the process ID of your program, and
do</para>
<screen>&prompt.user; <userinput>kill -ABRT pid</userinput>
<screen>&prompt.user; <userinput>kill -ABRT <replaceable>pid</replaceable></userinput>
</screen>
<para>where
@ -1147,7 +1147,7 @@ install:
<para>We can tell make which target we want to make by
typing:</para>
<screen>&prompt.user; <userinput>make target</userinput></screen>
<screen>&prompt.user; <userinput>make <replaceable>target</replaceable></userinput></screen>
<para><command>make</command> will then only look at that target
and ignore any others. For example, if we type
@ -1376,12 +1376,12 @@ DISTFILES= scheme-microcode+dist-7.3-freebsd.tgz
<command>gdb</command> (<application>GNU
debugger</application>). You start it up by typing</para>
<screen>&prompt.user; <userinput>gdb progname</userinput></screen>
<screen>&prompt.user; <userinput>gdb <replaceable>progname</replaceable></userinput></screen>
<para>although many people prefer to run it inside
<application>Emacs</application>. You can do this by:</para>
<screen><userinput>M-x gdb RET progname RET</userinput></screen>
<screen><userinput>M-x gdb RET <replaceable>progname</replaceable> RET</userinput></screen>
<para>Using a debugger allows you to run the program under more
controlled circumstances. Typically, you can step through the
@ -1543,7 +1543,7 @@ main() {
listings of core files and sweat over machine code manuals,
but now life is a bit easier. Incidentally, under FreeBSD and
other 4.4BSD systems, a core file is called
<filename>progname.core</filename> instead of just
<filename><replaceable>progname</replaceable>.core</filename> instead of just
<filename>core</filename>, to make it clearer which program a
core file belongs to.</para>
@ -1551,7 +1551,7 @@ main() {
the usual way. Instead of typing <command>break</command> or
<command>run</command>, type</para>
<screen>(gdb) <userinput>core progname.core</userinput></screen>
<screen>(gdb) <userinput>core <replaceable>progname</replaceable>.core</userinput></screen>
<para>If you are not in the same directory as the core file,
you will have to do <userinput>dir
@ -1609,7 +1609,7 @@ Cannot access memory at address 0x7020796d.
use <command>ps</command> to find the process ID for the
child, and do</para>
<screen>(gdb) <userinput>attach pid</userinput></screen>
<screen>(gdb) <userinput>attach <replaceable>pid</replaceable></userinput></screen>
<para>in <command>gdb</command>, and then debug as usual.</para>
@ -1851,7 +1851,7 @@ else if (pid == 0) { /* child */
if you are doing something outside Emacs and you want to
edit a file, you can just type in</para>
<screen>&prompt.user; <userinput>emacsclient filename</userinput>
<screen>&prompt.user; <userinput>emacsclient <replaceable>filename</replaceable></userinput>
</screen>
<para>and then you can edit the file in your