Changeset 64e0f6c4 in rtems


Ignore:
Timestamp:
Apr 2, 1999, 5:23:36 PM (22 years ago)
Author:
Joel Sherrill <joel.sherrill@…>
Branches:
4.10, 4.11, 4.8, 4.9, 5, master
Children:
65beca61
Parents:
5a8e90c5
Message:

Can now produce html, info, and PostScript? without errors. Links
between chapters are correct.

Location:
doc/rgdb_specs
Files:
7 edited

Legend:

Unmodified
Added
Removed
  • doc/rgdb_specs/Makefile

    r5a8e90c5 r64e0f6c4  
    6262
    6363intro.texi: intro.t Makefile
    64         $(BMENU) -p "Top" \
     64        $(BMENU) -c -p "Top" \
    6565            -u "Top" \
    66             -n "" ${*}.t
     66            -n "Document Revision History" ${*}.t
    6767
    6868revision.texi: revision.t Makefile
    69         $(BMENU) -p "Top" \
     69        $(BMENU) -c -p "Introduction" \
    7070            -u "Top" \
    71             -n "" ${*}.t
     71            -n "Objectives" ${*}.t
    7272
    7373objectives.texi: objectives.t Makefile
    74         $(BMENU) -p "Top" \
     74        $(BMENU) -c -p "Document Revision History" \
    7575            -u "Top" \
    76             -n "" ${*}.t
     76            -n "A Rapid Tour of GDB Internals" ${*}.t
    7777
    7878gdbinternals.texi: gdbinternals.t Makefile
    79         $(BMENU) -p "Top" \
     79        $(BMENU) -c -p "Implied Restrictions" \
    8080            -u "Top" \
    81             -n "" ${*}.t
     81            -n "Interfacing GDB with RTEMS as a Target" ${*}.t
    8282
    8383interfacing.texi: interfacing.t Makefile
    84         $(BMENU) -p "Top" \
     84        $(BMENU) -c -p "A Rapid Tour of GDB Internals" \
    8585            -u "Top" \
    86             -n "" ${*}.t
     86            -n "Communication with GDB" ${*}.t
    8787
    8888comm.texi: comm.t Makefile
    89         $(BMENU) -p "Top" \
     89        $(BMENU) -c -p "Interfacing GDB with RTEMS as a Target" \
    9090            -u "Top" \
    91             -n "" ${*}.t
     91            -n "RTEMS Debugger Server Daemon" ${*}.t
    9292
    9393daemon.texi: daemon.t Makefile
    94         $(BMENU) -p "Top" \
     94        $(BMENU) -c -p "Communication with GDB" \
    9595            -u "Top" \
    96             -n "" ${*}.t
     96            -n "Conclusion" ${*}.t
    9797
    9898conclusion.texi: conclusion.t Makefile
    99         $(BMENU) -p "Top" \
     99        $(BMENU) -c -p "Output of a Debug Session with the Prototype" \
    100100            -u "Top" \
    101101            -n "" ${*}.t
  • doc/rgdb_specs/comm.t

    r5a8e90c5 r64e0f6c4  
    55@c              Emmanuel Raguet <raguet@crf.canon.fr>
    66@c
    7 @C
     7@c
    88@c  $Id$
    99@c
  • doc/rgdb_specs/daemon.t

    r5a8e90c5 r64e0f6c4  
    1818handlers :
    1919
    20 @itemize @b
     20@itemize @bullet
    2121@item an initialization task which opens the sockets and runs the SUN RPC
    2222server. This task will also connect the interrupt handlers and launch the communication
     
    4848
    4949
    50 @subsection The INITIALIZATION task
     50@section The INITIALIZATION task
    5151
    5252This is the task that must be executed at the boot phase of RTEMS.
    5353It initializes the debug context. It must :
    5454
    55 @itemize @b
     55@itemize @bullet
    5656@item open the UDP sockets,
    5757@item run the SUN RPC server main loop,
     
    6565
    6666
    67 @subsection The COMMAND_MNGT task
     67@section The COMMAND_MNGT task
    6868
    6969This task is in charge of receiving the SUN RPC messages and executing
     
    8787
    8888
    89 @subsection The EVENT_MNGT task
     89@section The EVENT_MNGT task
    9090
    9191This task is in charge of managing events happening on the debuggee such as
     
    9696
    9797
    98 @subsection The DEBUG EXCEPTION handler
     98@section The DEBUG EXCEPTION handler
    9999
    100100This handler is connected to the DEBUG exception (INT 1 on Intel ix86).
    101101This exception is entered when :
    102102
    103 @itemize @b
     103@itemize @bullet
    104104@item executing a single-step instruction,
    105105@item hardware breakpoint condition is true,
     
    111111the exception . This implies :
    112112
    113 @itemize @b
     113@itemize @bullet
    114114@item We may sleep in this context,
    115115@item We have as many possible execution context for the DEBUG EXCEPTION handler as
     
    129129
    130130
    131 @subsection The BREAKPOINT EXCEPTION handler
     131@section The BREAKPOINT EXCEPTION handler
    132132
    133133This handler is connected to the BREAKPOINT exception (INT3 on Intel
     
    139139
    140140
    141 @subsection Synchronization Among Tasks and Exception Handlers
     141@section Synchronization Among Tasks and Exception Handlers
    142142
    143143The previous chapters have presented a simplified and static view of the various
     
    146146
    147147
    148 @subsubsection Implicit Synchronization Using Task Priorities
     148@subsection Implicit Synchronization Using Task Priorities
    149149
    150150This chapter is relevant on Uniprocessor System (UP) only. However, it will
     
    171171
    172172
    173 @subsubsection Explicit Synchronization
     173@subsection Explicit Synchronization
    174174
    175175This chapter will describe the synchronization variables that need to be implemented
     
    191191because the task that does V is not the task that has done the P.
    192192
    193 @itemize @b
     193@itemize @bullet
    194194@item @emph{WakeUpEventTask} : used by exception handler code to wake up the EVENT_MNGT
    195195task by doing a V operation on this object. When target code is running normally
    196196the EVENT_MNGT task sleeps due to a P operation on this semaphore,
    197197@item @emph{SerializeDebugEvent} : used to serialize events in a way compatible to
    198 what GDB expects. Before doing a V operation on @emph{WakeUpEventTask,} the
     198what GDB expects. Before doing a V operation on @emph{WakeUpEventTask}, the
    199199exception handler does a P on this semaphore to be sure processing of another
    200200exception is not in progress. Upon reception of a CONTINUE command, the COMMAND_MNGT
     
    212212@end itemize
    213213
    214 @subsection Open Issues
     214@section Open Issues
    215215
    216216Here are some problems we have faced while implementing our prototype :
     
    224224before calling @b{readMem/writeMem} can be temporarily sufficient but :
    225225
    226 @itemize @b
     226@itemize @bullet
    227227@item It will never work on MP system as it will rely on task priorities to insure
    228228that other task will not cause exceptions while we have removed the default
     
    249249to become inactive via @emph{rtems_task_suspend} but no way to get the full
    250250registers set for the thread. A partial context can be retrieved from the task
    251 @emph{Registers} data structure. On the other hand, relying on @emph{rtems_task_suspend
     251@emph{Registers} data structure. On the other hand, relying on @emph{rtems_task_suspend}
    252252will be a problem for the nano-kernel implementation.
    253253
     
    302302@end table
    303303
    304 @subsection Workarounds for Open Issues in Prototype
     304@section Workarounds for Open Issues in Prototype
    305305
    306306@table @b
     
    338338@end table
    339339
    340 @subsection Output of a Debug Session with the Prototype
     340@section Output of a Debug Session with the Prototype
    341341
    342342@example
     
    392392(gdb) c
    393393Continuing.
    394 {Switching to Rtems thread 134283270 (Not suspended) ( <= current target thread )]
     394Switching to Rtems thread 134283270 (Not suspended) ( <= current target thread )]
    395395Breakpoint 2, example1 (argument=4) at /rtems/c/src/tests/samples/debug/init.c:66
    39639666          toto += titi;
  • doc/rgdb_specs/gdbinternals.t

    r5a8e90c5 r64e0f6c4  
    120120figures will now be described showing the main steps of a debug session.
    121121
    122 @C XXX figure reference
     122@c XXX figure reference
    123123Figure @b{Debug session initialization} explains how the debugger connects to the target
    124124:
     
    137137@end enumerate
    138138
    139 @C XXX figure reference
     139@c XXX figure reference
    140140Figure @b{Breakpoint and process execution} explains how the debugger manages the
    141141breakpoints and controls the execution of a process :
     
    158158@end enumerate
    159159
    160 @C XXX figure reference
     160@c XXX figure reference
    161161Figure @b{Breakpoint and process execution} also shows the case of other ``CONTINUE''
    162162commands (remember that the ``DEBUG'' opcode has been replaced by the right
     
    175175@end enumerate
    176176
    177 @C XXX figure reference
     177@c XXX figure reference
    178178Figure @b{Detach a process and close a connection} explains how the debugger disconnects from
    179179a target :
     
    189189the host debugger on the target are only simple actions which look like :
    190190
    191 @itemize @b
     191@itemize @bullet
    192192@item read/write code,
    193193@item read/write data,
  • doc/rgdb_specs/interfacing.t

    r5a8e90c5 r64e0f6c4  
    1111@chapter Interfacing GDB with RTEMS as a Target
    1212
    13 @C XXX figure reference
     13@c XXX figure reference
    1414So, basically, porting GDB to RTEMS environment requires implementing
    1515the functions contained in the target_ops structure. The native debugger implementation
     
    3030of some commands required to implement the previously described functions :
    3131
    32 @itemize @b
     32@itemize @bullet
    3333@item set up a connection with a target,
    3434@item close a connection,
     
    4646needs) :
    4747
    48 @itemize @b
     48@itemize @bullet
    4949@item PTRACE_PEEKTEXT, PTRACE_PEEKDATA : read word at address,
    5050@item PTRACE_POKETEXT, PTRACE_POKEDATA :write word at address,
     
    6060as described after :
    6161
    62 @itemize @b
     62@itemize @bullet
    6363@item get current task registers,
    6464@item set current task registers,
  • doc/rgdb_specs/objectives.t

    r5a8e90c5 r64e0f6c4  
    1111@chapter Objectives
    1212
    13 @C XXX reference
     13@c XXX reference
    1414This section is intended to clearly define the current objectives of our work.
    1515First, we will try here to list some ambitious requirements for the debugger
     
    2626
    2727
    28 @subsection List of Requirements
     28@section List of Requirements
    2929
    3030We will identify here possible requirements for the type of debug that may be
     
    7373@end table
    7474
    75 @subsection Requirements Analysis
     75@section Requirements Analysis
    7676
    7777@table @b
     
    8181files type, target processor type as :
    8282
    83 @itemize @b
     83@itemize @bullet
    8484
    8585@item the binary format must be understood by GDB (to find debugging information).
     
    215215@end table
    216216
    217 @subsection Requirements Selection
    218 
    219 
    220 @subsubsection Requirement We Will Take Into Account For the First Implementation
     217@section Requirements Selection
     218
     219
     220@subsection Requirement We Will Take Into Account For the First Implementation
    221221
    222222@table @b
     
    245245@end table
    246246
    247 @subsubsection Requirements We Will Not Implement
     247@subsection Requirements We Will Not Implement
    248248
    249249@table @b
     
    277277@end table
    278278
    279 @subsection Implied Restrictions
     279@section Implied Restrictions
    280280
    281281High priority level must be used for these features :
    282282
    283 @itemize @b
     283@itemize @bullet
    284284
    285285@item FreeBSD interrupt handling thread,
     
    294294priority to each of these tasks as follow :
    295295
    296 @itemize @b
     296@itemize @bullet
    297297
    298298@item FreeBSD stack (high priority)
  • doc/rgdb_specs/revision.t

    r5a8e90c5 r64e0f6c4  
    1111@chapter Document Revision History
    1212
    13 @ubaraccent{Current release} :
     13@b{Current release} :
    1414
    15 @itemize @b
     15@itemize @bullet
    1616@item Current applicable release is 2.0.
    1717@end itemize
    18 @ubaraccent{Existing releases} :
    1918
    20 @itemize @b
     19@b{Existing releases} :
     20
     21@itemize @bullet
    2122@item 0.1 : Released the 29/09/98. First draft of this document.
     23
    2224@item 0.2 : Released the 05/10/98. Second draft version.
     25
    2326@item 1.0 : Released the 08/10/98. Version Approved internally.
     27
    2428@item 1.1 : Released the 13/13/98. Version Distributed for comments.
     29
    2530@item 2.0 : Released the 01/11/98. Version including modifications related
    2631to comments we have got from the RTEMS mailing list. It also contains a
    2732more precise description of RGDBSD as we now have a first prototype,
     33
    2834@end itemize
    2935
    30 @ubaraccent{Planned releases} :
     36@b{Planned releases} :
    3137
    32 @itemize @b
     38@itemize @bullet
    3339@item 2.1 Final specification release intended to include a second round
    3440of comments,
Note: See TracChangeset for help on using the changeset viewer.