OpenCores
URL https://opencores.org/ocsvn/openrisc_me/openrisc_me/trunk

Subversion Repositories openrisc_me

[/] [openrisc/] [trunk/] [gnu-src/] [gdb-7.2/] [gdb/] [doc/] [gdbint.info-1] - Diff between revs 330 and 342

Show entire file | Details | Blame | View Log

Rev 330 Rev 342
Line 1... Line 1...
This is gdbint.info, produced by makeinfo version 4.8 from
This is gdbint.info, produced by makeinfo version 4.13 from
./gdbint.texinfo.
./gdbint.texinfo.
 
 
INFO-DIR-SECTION Software development
INFO-DIR-SECTION Software development
START-INFO-DIR-ENTRY
START-INFO-DIR-ENTRY
* Gdb-Internals: (gdbint).      The GNU debugger's internals.
* Gdb-Internals: (gdbint).      The GNU debugger's internals.
Line 924... Line 924...
a new interface overcoming the issues with the notification mechanisms
a new interface overcoming the issues with the notification mechanisms
previously available.  This new interface needed to be strongly typed,
previously available.  This new interface needed to be strongly typed,
easy to extend, and versatile enough to be used as the standard
easy to extend, and versatile enough to be used as the standard
interface when adding new notifications.
interface when adding new notifications.
 
 
   See *Note GDB Observers:: for a brief description of the observers
   See *note GDB Observers:: for a brief description of the observers
currently implemented in GDB. The rationale for the current
currently implemented in GDB. The rationale for the current
implementation is also briefly discussed.
implementation is also briefly discussed.
 
 


File: gdbint.info,  Node: User Interface,  Next: libgdb,  Prev: Algorithms,  Up: Top
File: gdbint.info,  Node: User Interface,  Next: libgdb,  Prev: Algorithms,  Up: Top
Line 2117... Line 2117...
 
 
The IBM RS/6000 running AIX uses an object file format called XCOFF.
The IBM RS/6000 running AIX uses an object file format called XCOFF.
The COFF sections, symbols, and line numbers are used, but debugging
The COFF sections, symbols, and line numbers are used, but debugging
symbols are `dbx'-style stabs whose strings are located in the `.debug'
symbols are `dbx'-style stabs whose strings are located in the `.debug'
section (rather than the string table).  For more information, see
section (rather than the string table).  For more information, see
*Note Top: (stabs)Top.
*note Top: (stabs)Top.
 
 
   The shared library scheme has a clean interface for figuring out what
   The shared library scheme has a clean interface for figuring out what
shared libraries are in use, but the catch is that everything which
shared libraries are in use, but the catch is that everything which
refers to addresses (symbol tables and breakpoints at least) needs to be
refers to addresses (symbol tables and breakpoints at least) needs to be
relocated for both shared libraries and the main executable.  At least
relocated for both shared libraries and the main executable.  At least
Line 4257... Line 4257...
     feature-specific macros.  It was introduced in haste and we are
     feature-specific macros.  It was introduced in haste and we are
     repenting at leisure.
     repenting at leisure.
 
 
`I386_USE_GENERIC_WATCHPOINTS'
`I386_USE_GENERIC_WATCHPOINTS'
     An x86-based target can define this to use the generic x86
     An x86-based target can define this to use the generic x86
     watchpoint support; see *Note I386_USE_GENERIC_WATCHPOINTS:
     watchpoint support; see *note I386_USE_GENERIC_WATCHPOINTS:
     Algorithms.
     Algorithms.
 
 
`gdbarch_in_function_epilogue_p (GDBARCH, ADDR)'
`gdbarch_in_function_epilogue_p (GDBARCH, ADDR)'
     Returns non-zero if the given ADDR is in the epilogue of a
     Returns non-zero if the given ADDR is in the epilogue of a
     function.  The epilogue of a function is defined as the part of a
     function.  The epilogue of a function is defined as the part of a
Line 4624... Line 4624...
a processor or development board.  "Target descriptions" provide a
a processor or development board.  "Target descriptions" provide a
mechanism for the user to tell GDB more about what their target
mechanism for the user to tell GDB more about what their target
supports, or for the target to tell GDB directly.
supports, or for the target to tell GDB directly.
 
 
   For details on writing, automatically supplying, and manually
   For details on writing, automatically supplying, and manually
selecting target descriptions, see *Note Target Descriptions:
selecting target descriptions, see *note Target Descriptions:
(gdb)Target Descriptions.  This section will cover some related topics
(gdb)Target Descriptions.  This section will cover some related topics
about the GDB internals.
about the GDB internals.
 
 
* Menu:
* Menu:
 
 
Line 4657... Line 4657...
`' element is handled first, to determine which
`' element is handled first, to determine which
architecture's gdbarch initialization routine is called to create the
architecture's gdbarch initialization routine is called to create the
new architecture.  Then the initialization routine is called, and has a
new architecture.  Then the initialization routine is called, and has a
chance to adjust the constructed architecture based on the contents of
chance to adjust the constructed architecture based on the contents of
the target description.  For instance, it can recognize any properties
the target description.  For instance, it can recognize any properties
set by a `to_read_description' routine.  Also see *Note Adding Target
set by a `to_read_description' routine.  Also see *note Adding Target
Described Register Support::.
Described Register Support::.
 
 


File: gdbint.info,  Node: Adding Target Described Register Support,  Prev: Target Descriptions Implementation,  Up: Target Descriptions
File: gdbint.info,  Node: Adding Target Described Register Support,  Prev: Target Descriptions Implementation,  Up: Target Descriptions
 
 
Line 4929... Line 4929...
the same.  These macros should be defined (or left undefined) in
the same.  These macros should be defined (or left undefined) in
`nm-SYSTEM.h'.
`nm-SYSTEM.h'.
 
 
`I386_USE_GENERIC_WATCHPOINTS'
`I386_USE_GENERIC_WATCHPOINTS'
     An x86-based machine can define this to use the generic x86
     An x86-based machine can define this to use the generic x86
     watchpoint support; see *Note I386_USE_GENERIC_WATCHPOINTS:
     watchpoint support; see *note I386_USE_GENERIC_WATCHPOINTS:
     Algorithms.
     Algorithms.
 
 
`SOLIB_ADD (FILENAME, FROM_TTY, TARG, READSYMS)'
`SOLIB_ADD (FILENAME, FROM_TTY, TARG, READSYMS)'
     Define this to expand into an expression that will cause the
     Define this to expand into an expression that will cause the
     symbols in FILENAME to be added to GDB's symbol table.  If
     symbols in FILENAME to be added to GDB's symbol table.  If

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.