Changeset 7b597b85 in rtems


Ignore:
Timestamp:
02/10/99 18:54:14 (24 years ago)
Author:
Joel Sherrill <joel.sherrill@…>
Branches:
4.10, 4.11, 4.8, 4.9, 5, master
Children:
9414e3f8
Parents:
89d177eb
Message:

Now generates HTML, PostScript?, and info correctly.

Location:
doc/rtems_gdb
Files:
7 edited

Legend:

Unmodified
Added
Removed

  • doc/rtems_gdb/Makefile

    r89d177eb r7b597b85  
    2020
    2121GENERATED_FILES= \
    22     intro.t swarch.t started.t commands.t trouble.t example.t
    23 
     22    intro.texi swarch.texi started.texi commands.texi trouble.texi example.texi
    2423
    2524FILES=$(PROJECT).texi $(GENERATED_FILES)
    … …  
    6463        $(BMENU) -p "Top" \
    6564            -u "Top" \
    66             -n "" ${*}.t
     65            -n "Software Architecture" ${*}.t
    6766
    6867swarch.texi: swarch.t Makefile
    69         $(BMENU) -p "Top" \
     68        $(BMENU) -p "Introduction" \
     69            -u "Top" \
     70            -n "Getting Started" ${*}.t
     71
     72started.texi: started.t Makefile
     73        $(BMENU) -p "Software Architecture" \
     74            -u "Top" \
     75            -n "Commands" ${*}.t
     76
     77commands.texi: commands.t Makefile
     78        $(BMENU) -p "Getting Started Attaching To The System" \
     79            -u "Top" \
     80            -n "Troubleshooting" ${*}.t
     81
     82trouble.texi: trouble.t Makefile
     83        $(BMENU) -p "Commands Thread control" \
     84            -u "Top" \
     85            -n "Debug Session Example" ${*}.t
     86
     87example.texi: example.t Makefile
     88        $(BMENU) -p "Troubleshooting Debug server not present" \
    7089            -u "Top" \
    7190            -n "" ${*}.t
    7291
    73 started.texi: started.t Makefile
    74         $(BMENU) -p "Top" \
    75             -u "Top" \
    76             -n "" ${*}.t
    77 
    78 commands.texi: commands.t Makefile
    79         $(BMENU) -p "Top" \
    80             -u "Top" \
    81             -n "" ${*}.t
    82 
    83 trouble.texi: trouble.t Makefile
    84         $(BMENU) -p "Top" \
    85             -u "Top" \
    86             -n "" ${*}.t
    87 
    88 example.texi: example.t Makefile
    89         $(BMENU) -p "Top" \
    90             -u "Top" \
    91             -n "" ${*}.t
    92 

  • doc/rtems_gdb/commands.t

    r89d177eb r7b597b85  
    77@c
    88
    9 @section Commands
     9@chapter Commands
    1010
    1111The usual GDB commands are available to display or modify data structures and
    … …  
    1919
    2020
    21 @subsection Host-target connection control
     21@section Host-target connection control
    2222
    23 @itemize
     23@itemize @bullet
    2424@item (gdb) setrpcmode sun : specifies the SUN RPC type.
    2525@item (gdb) setdaemontype rdbg : specifies the RDBG debug server type.
    … …  
    2727@end itemize
    2828
    29 @subsection System status information
     29@section System status information
    3030
    31 @itemize
     31@itemize @bullet
    3232@item (gdb) info threads : gives a list of all threads in the debuggee,
    3333their names, identifiers and states. It also indicates which thread is
    … …  
    3636
    3737
    38 @subsection Thread control
     38@section Thread control
    3939
    40 @itemize
     40@itemize @bullet
    4141@item (gdb) thread target [id] : allows the user to get/set the target thread.
    4242The argument id is either the thread's symbolic name or its local identifier.

  • doc/rtems_gdb/example.t

    r89d177eb r7b597b85  
    77@c
    88
    9 @section Debug Session Example
     9@chapter Debug Session Example
    1010
    1111@example

  • doc/rtems_gdb/intro.t

    r89d177eb r7b597b85  
    1717to be familiar with GNU GDB.
    1818
     19The RTEMS project would like to thank Emmanuel Raguet (raguet@crf.canon.fr)
     20and Eric Valette (valette@crf.canon.fr) of the Canon Research Centre
     21France S.A. for developing and documenting RTEMS/GDB and submitting it.
     22

  • doc/rtems_gdb/rtems_gdb.texi

    r89d177eb r7b597b85  
    6565
    6666@include intro.texi
    67 @include target.texi
    68 @include makefiles.texi
    69 @include linkcmds.texi
    70 @include support.texi
    71 @include init.texi
    72 @include console.texi
    73 @include clock.texi
    74 @include timer.texi
    75 @include rtc.texi
    76 @include nvmem.texi
    77 @include network.texi
    78 @include shmsupp.texi
    79 @include analog.texi
    80 @include discrete.texi
     67@include swarch.texi
     68@include started.texi
     69@include commands.texi
     70@include trouble.texi
     71@include example.texi
    8172
    8273@ifinfo
    … …  
    8475@top rtems_gdb
    8576
    86 This is the online version of the Getting Started with RTEMS for C/C++ Users.
     77This is the online version of the RTEMS/GDB User's Guide.
    8778
    8879@menu
    8980* Introduction::
    90 * Target Dependent Files::
    91 * Makefiles::
    92 * Linker Script::
    93 * Miscellaneous Support Files::
    94 * Initialization Code::
    95 * Console Driver::
    96 * Clock Driver::
    97 * Timer Driver::
    98 * Real-Time Clock Driver::
    99 * Networking Driver::
    100 * Non-Volatile Memory Driver::
    101 * Shared Memory Support Driver::
    102 * Analog Driver::
    103 * Discrete Driver::
     81* Software Architecture::
     82* Getting Started::
     83* Commands::
     84* Troubleshooting::
     85* Debug Session Example::
    10486@end menu
    10587

  • doc/rtems_gdb/started.t

    r89d177eb r7b597b85  
    88
    99
    10 @section Getting Started
     10@chapter Getting Started
    1111
    1212This section describes the steps which are necessary to set up a
    … …  
    1414
    1515
    16 @subsection Compiling The System Components
     16@section Compiling The System Components
    1717
    1818The components that need to be debugged have to be compiled with the -g option
    … …  
    2121
    2222
    23 @subsection Starting a debugging session
     23@section Starting a debugging session
    2424
    2525After having launched GDB, the user must connect to the RTEMS target with the
    … …  
    2727
    2828@example
    29 
    3029(gdb) setrpcmode sun
    31 
    3230(gdb) setdaemontype rdbg
    33 
    3431(gdb) target rtems target-name
    35 
    3632@end example
    3733
    … …  
    4339
    4440
    45 @subsection Attaching To The System
     41@section Attaching To The System
    4642
    4743The entire target system is viewed as a single multi-threaded process,

  • doc/rtems_gdb/trouble.t

    r89d177eb r7b597b85  
    88
    99
    10 @section Troubleshooting
     10@chapter Troubleshooting
    1111
    1212This section describes symptoms in some situations where the debugger does not
    … …  
    1414
    1515
    16 @subsection Target machine name unknown on the host
     16@section Target machine name unknown on the host
    1717
    1818RTEMS/GDB fails to connect to target machine named my_target:
    … …  
    2929
    3030
    31 @subsection{Debug server not present
     31@section Debug server not present
    3232
    3333The target rtems command fails:
    3434
    3535@example
    36 
    37 (gdb) target rtems my\_target
     36(gdb) target rtems my_target
    3837
    3938Attaching remote machine across net... RPC timed out. Couldn't connect
    4039to remote target
    41 
    4240@end example
    4341
Note: See TracChangeset for help on using the changeset viewer.