HP gnu source-level debugger 5992-4701 Manual do Utilizador Página 289

  • Descarregar
  • Adicionar aos meus manuais
  • Imprimir
  • Página
    / 369
  • Índice
  • MARCADORES
  • Avaliado. / 5. Com base em avaliações de clientes
Vista de página 288
end
define hook-continue
handle SIGLARM pass
end
You can define a hook for any single-word command in GDB, and not for command
aliases; Also you should define a hook for the basic command name, for example,
backtrace rather than bt. If an error occurs during the execution of your hook,
execution of GDB commands stops and GDB issues a prompt (before the command
that you actually typed had a chance to run).
If you try to define a hook which does not match any known command, GDB issues a
warning from the define command.
18.3 Command files
A command file for GDB is a file of lines that are GDB commands. Comments (lines
starting with #) may also be included. An empty line in a command file does nothing;
it does not mean to repeat the last command, as it would from the terminal.
When you start GDB, it executes commands from its init files. These are files named
.gdbinit on UNIX. During startup, GDB does the following:
1. Read the init file (if any) in your home directory.
4
2. Process command-line options and operands.
3. Read the init file (if any) in the current working directory,
4. Read the init file (if any) in the /tmp directory if the GDB_PROCESS_TMP_GDBINIT
environment variable is set.
5. Read command files specified by the `-x' option.
The init file in your home directory can set options (such as `set complaints') that affect
subsequent processing of command line options and operands. Init files are not executed
if you use the `-nx' option (see “Choosing modes” (page 27)).
It can be useful to create a `.gdbinit' file in the directory where you are debugging an
application. This file will set the actions that apply for this application.
For example, one might add lines like:
dir /usr/src/path/to/source/files
to add source directories or:
break fatal
to set breakpoints on fatal error routines or diagnostic routines.
On some configurations of GDB, the init file is known by a different name (these are
typically environments where a specialized form of GDB may need to coexist with
other forms, hence a different name for the specialized version's init file). These are
the environments with special init file names:
18.3 Command files 289
Vista de página 288
1 2 ... 284 285 286 287 288 289 290 291 292 293 294 ... 368 369

Comentários a estes Manuais

Sem comentários

Conceptronic C20-150 manuales

Manuales del propietario y guías del usuario para Hdd / ssd recintos Conceptronic C20-150.
Ofrecemos 1 manuales en pdf Conceptronic C20-150 para descargar gratis por tipos de documentos: Ficha de datos


Tabla de contenidos





Más productos y manuales para Hdd / ssd recintos Conceptronic

Modelos Tipo de documento
C20-258 Ficha de datos   Conceptronic 2,5" Harddisk Box Mini Violet USB powered, 3 paginas
C05-210 Ficha de datos   Conceptronic 3,5 inch USB hard disk box for SATA hard disk, 3 paginas
C05-500 Ficha de datos   Conceptronic 2,5 / 3,5 inch hard disk docking station eSATA/USB, 3 paginas
CHD3SATA Ficha de datos   Conceptronic Serial ATA External Hard disk box 3.5 “., 1 paginas
C10-393 Ficha de datos   Conceptronic Grab'n'GO 2.5” Hard Disk Box eSATA/USB 2.0, 3 paginas
C05-326 Ficha de datos   Conceptronic USB SATA HDD 2.5" BLACK USB powered, 3 paginas
C10-135 Ficha de datos   Conceptronic 3,5 inch USB/e-SATA hard disk box, 3 paginas
C05-106 Ficha de datos   Conceptronic USB 2.0 & Firewire Harddisk Box 3.5", 1 paginas
C05-324 Ficha de datos   Conceptronic 3,5 inch HardDiskBox DualBay, 3 paginas
C20-253 Ficha de datos   Conceptronic 2,5" Harddisk Box Mini Blue USB powered, 3 paginas
C05-209 Ficha de datos   Conceptronic 2,5 inch USB hard disk box for SATA hard disk, 3 paginas
CHD3U Ficha de datos   Conceptronic USB 2.0 Hard Disk Box 3.5", 1 paginas