+Tue Aug 18 15:59:13 1992 Roland H. Pesch (pesch@fowanton.cygnus.com)
+
+ * gdbinv-s.m4.in: refrain from using @cartouche for just a few
+ examples (not consistent w others).
+ gdb.texinfo: issue disclaimer paragraph on cmdline options only
+ for generic vn of doc
+
Tue Aug 18 14:53:27 1992 Ian Lance Taylor (ian@cygnus.com)
* Makefile.in: always create installation directories.
You can also run @code{_GDBP__} with a variety of arguments and options,
to specify more of your debugging environment at the outset.
+_if__(_GENERIC__)
The command-line options described here are designed
to cover a variety of situations; in some environments, some of these
options may effectively be unavailable.
+_fi__(_GENERIC__)
The most usual way to start _GDBN__ is with one argument,
specifying an executable program:
for example, @samp{asyncstr 2} below runs @code{asyncstr} on
@code{COM2}.
-@cartouche
-@example
+@smallexample
(eg-C:\H8300\TEST) mode com2:9600,n,8,1,p
Resident portion of MODE loaded
COM2: 9600, n, 8, 1, p
(eg-C:\H8300\TEST) asynctsr 2
-@end example
-@end cartouche
+@end smallexample
@quotation
@emph{Warning:} We have noticed a bug in PC-NFS that conflicts with
@code{symbol-file}. These commands, and @code{load} itself, are
described in @ref{Files,,Commands to Specify Files}.)
-@cartouche
-@example
+@smallexample
(eg-C:\H8300\TEST) _GDBP__ t.x
GDB is free software and you are welcome to distribute copies
of it under certain conditions; type "show copying" to see
.text : 0x8000 .. 0xabde ***********
.data : 0xabde .. 0xad30 *
.stack : 0xf000 .. 0xf014 *
-@end example
-@end cartouche
+@end smallexample
At this point, you're ready to run or debug your program. From here on,
you can use all the usual _GDBN__ commands. The @code{break} command