Subversion Repositories openrisc_2011-10-31

INFO-DIR-SECTION Software development

INFO-DIR-SECTION Software development

START-INFO-DIR-ENTRY

START-INFO-DIR-ENTRY

* Gdb: (gdb).                     The GNU debugger.

* Gdb: (gdb).                     The GNU debugger.

END-INFO-DIR-ENTRY

END-INFO-DIR-ENTRY

developing GNU and promoting software freedom."

developing GNU and promoting software freedom."

   This file documents the GNU debugger GDB.

   This file documents the GNU debugger GDB.

   This is the Ninth Edition, of `Debugging with GDB: the GNU

   This is the Ninth Edition, of `Debugging with GDB: the GNU

   Copyright (C) 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996,

   Copyright (C) 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996,

1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,

1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,

2010 Free Software Foundation, Inc.

2010 Free Software Foundation, Inc.

   (1) This is a way of removing one word from the stack, on machines

   (1) This is a way of removing one word from the stack, on machines

where stacks grow downward in memory (most machines, nowadays).  This

where stacks grow downward in memory (most machines, nowadays).  This

assumes that the innermost stack frame is selected; setting `$sp' is

assumes that the innermost stack frame is selected; setting `$sp' is

not allowed when other stack frames are selected.  To pop entire frames

not allowed when other stack frames are selected.  To pop entire frames

off the stack, regardless of machine architecture, use `return'; see

off the stack, regardless of machine architecture, use `return'; see

File: gdb.info,  Node: Floating Point Hardware,  Next: Vector Unit,  Prev: Registers,  Up: Data

File: gdb.info,  Node: Floating Point Hardware,  Next: Vector Unit,  Prev: Registers,  Up: Data

10.13 Floating Point Hardware

10.13 Floating Point Hardware

hardware, operating system, and process.  Each value's purpose is

hardware, operating system, and process.  Each value's purpose is

identified by an integer tag; the meanings are well-known but

identified by an integer tag; the meanings are well-known but

system-specific.  Depending on the configuration and operating system

system-specific.  Depending on the configuration and operating system

facilities, GDB may be able to show you this information.  For remote

facilities, GDB may be able to show you this information.  For remote

targets, this functionality may further depend on the remote stub's

targets, this functionality may further depend on the remote stub's

vector read::.

vector read::.

`info auxv'

`info auxv'

     Display the auxiliary vector of the inferior, which can be either a

     Display the auxiliary vector of the inferior, which can be either a

     live process or a core dump file.  GDB prints each tag value

     live process or a core dump file.  GDB prints each tag value

     in hexadecimal for an unrecognized tag.

     in hexadecimal for an unrecognized tag.

   On some targets, GDB can access operating-system-specific information

   On some targets, GDB can access operating-system-specific information

and display it to user, without interpretation.  For remote targets,

and display it to user, without interpretation.  For remote targets,

this functionality depends on the remote stub's support of the

this functionality depends on the remote stub's support of the

`info os'

`info os'

     List the types of OS information available for the target.  If the

     List the types of OS information available for the target.  If the

     target does not return a list of possible types, this command will

     target does not return a list of possible types, this command will

     report an error.

     report an error.

N, maximum number of finds

N, maximum number of finds

     The maximum number of matches to print.  The default is to print

     The maximum number of matches to print.  The default is to print

     all finds.

     all finds.

   You can use strings as search values.  Quote them with double-quotes

   You can use strings as search values.  Quote them with double-quotes

   The address of each match found is printed as well as a count of the

   The address of each match found is printed as well as a count of the

number of matches found.

number of matches found.

   The address of the last value found is stored in convenience variable

   The address of the last value found is stored in convenience variable

later, and then provide a different definition after that.  Thus, at

later, and then provide a different definition after that.  Thus, at

different points in the program, a macro may have different

different points in the program, a macro may have different

definitions, or have no definition at all.  If there is a current stack

definitions, or have no definition at all.  If there is a current stack

frame, GDB uses the macros in scope at that frame's source code line.

frame, GDB uses the macros in scope at that frame's source code line.

Otherwise, GDB uses the macros in scope at the current listing location;

Otherwise, GDB uses the macros in scope at the current listing location;

   Whenever GDB evaluates an expression, it always expands any macro

   Whenever GDB evaluates an expression, it always expands any macro

invocations present in the expression.  GDB also provides the following

invocations present in the expression.  GDB also provides the following

commands for working with macros explicitly.

commands for working with macros explicitly.

   The tracepoint facility is currently available only for remote

   The tracepoint facility is currently available only for remote

targets.  *Note Targets::.  In addition, your remote target must know

targets.  *Note Targets::.  In addition, your remote target must know

how to collect trace data.  This functionality is implemented in the

how to collect trace data.  This functionality is implemented in the

remote stub; however, none of the stubs distributed with GDB support

remote stub; however, none of the stubs distributed with GDB support

tracepoints as of this writing.  The format of the remote packets used

tracepoints as of this writing.  The format of the remote packets used

   It is also possible to get trace data from a file, in a manner

   It is also possible to get trace data from a file, in a manner

reminiscent of corefiles; you specify the filename, and use `tfind' to

reminiscent of corefiles; you specify the filename, and use `tfind' to

search through the file.  *Note Trace Files::, for more details.

search through the file.  *Note Trace Files::, for more details.

     overlay's instructions, appearing at the overlay's load address,

     overlay's instructions, appearing at the overlay's load address,

     not its mapped address.  However, each overlay's instructions must

     not its mapped address.  However, each overlay's instructions must

     be relocated and its symbols defined as if the overlay were at its

     be relocated and its symbols defined as if the overlay were at its

     mapped address.  You can use GNU linker scripts to specify

     mapped address.  You can use GNU linker scripts to specify

     different load and relocation addresses for pieces of your

     different load and relocation addresses for pieces of your

     Description.

     Description.

   * The procedure for loading executable files onto your system must

   * The procedure for loading executable files onto your system must

     be able to load their contents into the larger address space as

     be able to load their contents into the larger address space as

     well as the instruction and data spaces.

     well as the instruction and data spaces.

     functions and variables at their load addresses.

     functions and variables at their load addresses.

`overlay auto'

`overlay auto'

     Enable "automatic" overlay debugging.  In this mode, GDB consults

     Enable "automatic" overlay debugging.  In this mode, GDB consults

     a data structure the overlay manager maintains in the inferior to

     a data structure the overlay manager maintains in the inferior to

     Overlay Debugging::.

     Overlay Debugging::.

`overlay load-target'

`overlay load-target'

`overlay load'

`overlay load'

     Re-read the overlay table from the inferior.  Normally, GDB

     Re-read the overlay table from the inferior.  Normally, GDB

     You must specify `set overload-resolution off' in order to use an

     You must specify `set overload-resolution off' in order to use an

     explicit function signature to call an overloaded function, as in

     explicit function signature to call an overloaded function, as in

          p 'foo(char,int)'('x', 13)

          p 'foo(char,int)'('x', 13)

     Command Completion: Completion.

     Command Completion: Completion.

  4. GDB understands variables declared as C++ references; you can use

  4. GDB understands variables declared as C++ references; you can use

     them in expressions just as you do in C++ source--they are

     them in expressions just as you do in C++ source--they are

     automatically dereferenced.

     automatically dereferenced.

`set overload-resolution on'

`set overload-resolution on'

     Enable overload resolution for C++ expression evaluation.  The

     Enable overload resolution for C++ expression evaluation.  The

     default is on.  For overloaded functions, GDB evaluates the

     default is on.  For overloaded functions, GDB evaluates the

     arguments and searches for a function whose signature matches the

     arguments and searches for a function whose signature matches the

     C++ Expressions: C Plus Plus Expressions, for details).  If it

     C++ Expressions: C Plus Plus Expressions, for details).  If it

     cannot find a match, it emits a message.

     cannot find a match, it emits a message.

`set overload-resolution off'

`set overload-resolution off'

     Disable overload resolution for C++ expression evaluation.  For

     Disable overload resolution for C++ expression evaluation.  For

point computations, error checking in decimal float operations ignores

point computations, error checking in decimal float operations ignores

underflow, overflow and divide by zero exceptions.

underflow, overflow and divide by zero exceptions.

   In the PowerPC architecture, GDB provides a set of pseudo-registers

   In the PowerPC architecture, GDB provides a set of pseudo-registers

to inspect `_Decimal128' values stored in floating point registers.

to inspect `_Decimal128' values stored in floating point registers.

File: gdb.info,  Node: D,  Next: Objective-C,  Prev: C,  Up: Supported Languages

File: gdb.info,  Node: D,  Next: Objective-C,  Prev: C,  Up: Supported Languages

15.4.2 D

15.4.2 D

15.4.3 Objective-C

15.4.3 Objective-C

------------------

------------------

This section provides information about some commands and command

This section provides information about some commands and command

more commands specific to Objective-C support.

more commands specific to Objective-C support.

* Menu:

* Menu:

* Method Names in Commands::

* Method Names in Commands::

15.4.4.2 Fortran Defaults

15.4.4.2 Fortran Defaults

.........................

.........................

Fortran symbols are usually case-insensitive, so GDB by default uses

Fortran symbols are usually case-insensitive, so GDB by default uses

case-insensitive matches for Fortran symbols.  You can change that with

case-insensitive matches for Fortran symbols.  You can change that with

details.

details.

File: gdb.info,  Node: Special Fortran Commands,  Prev: Fortran Defaults,  Up: Fortran

File: gdb.info,  Node: Special Fortran Commands,  Prev: Fortran Defaults,  Up: Fortran

`break LINESPEC task TASKNO'

`break LINESPEC task TASKNO'

`break LINESPEC task TASKNO if ...'

`break LINESPEC task TASKNO if ...'

     These commands are like the `break ... thread ...' command (*note

     These commands are like the `break ... thread ...' command (*note

     Thread Stops::).  LINESPEC specifies source lines, as described in

     Thread Stops::).  LINESPEC specifies source lines, as described in

     Use the qualifier `task TASKNO' with a breakpoint command to

     Use the qualifier `task TASKNO' with a breakpoint command to

     specify that you only want GDB to stop the program when a

     specify that you only want GDB to stop the program when a

     particular Ada task reaches this breakpoint.  TASKNO is one of the

     particular Ada task reaches this breakpoint.  TASKNO is one of the

     numeric task identifiers assigned by GDB, shown in the first

     numeric task identifiers assigned by GDB, shown in the first

          Symbol p1 is a local variable in register $ebx, length 4.

          Symbol p1 is a local variable in register $ebx, length 4.

          Symbol nline is a local variable in register $edx, length 4.

          Symbol nline is a local variable in register $edx, length 4.

          Symbol repeat is a local variable at frame offset -8, length 4.

          Symbol repeat is a local variable at frame offset -8, length 4.

     This command is especially useful for determining what data to

     This command is especially useful for determining what data to

     Actions.

     Actions.

`info source'

`info source'

     Show information about the current source file--that is, the

     Show information about the current source file--that is, the

     source file for the function containing the current point of

     source file for the function containing the current point of

`jump LINESPEC'

`jump LINESPEC'

`jump LOCATION'

`jump LOCATION'

     Resume execution at line LINESPEC or at address given by LOCATION.

     Resume execution at line LINESPEC or at address given by LOCATION.

     Execution stops again immediately if there is a breakpoint there.

     Execution stops again immediately if there is a breakpoint there.

     `tbreak' command in conjunction with `jump'.  *Note Setting

     `tbreak' command in conjunction with `jump'.  *Note Setting

     Breakpoints: Set Breaks.

     Breakpoints: Set Breaks.

     The `jump' command does not change the current stack frame, or the

     The `jump' command does not change the current stack frame, or the

     stack pointer, or the contents of any memory location or any

     stack pointer, or the contents of any memory location or any

   * The executable contains a "build ID", a unique bit string that is

   * The executable contains a "build ID", a unique bit string that is

     also present in the corresponding debug info file.  (This is

     also present in the corresponding debug info file.  (This is

     supported only on some operating systems, notably those which use

     supported only on some operating systems, notably those which use

     the ELF format for binary files and the GNU Binutils.)  For more

     the ELF format for binary files and the GNU Binutils.)  For more

     details about this feature, see the description of the `--build-id'

     details about this feature, see the description of the `--build-id'

     (ld.info)Options.  The debug info file's name is not specified

     (ld.info)Options.  The debug info file's name is not specified

     explicitly by the build ID, but can be computed from the build ID,

     explicitly by the build ID, but can be computed from the build ID,

     see below.

     see below.

   Depending on the way the debug info file is specified, GDB uses two

   Depending on the way the debug info file is specified, GDB uses two

                  run

                  run

     works; however, you cannot assume that a specific memory map,

     works; however, you cannot assume that a specific memory map,

     device drivers, or even basic I/O is available, although some

     device drivers, or even basic I/O is available, although some

     simulators do provide these.  For info about any

     simulators do provide these.  For info about any

     processor-specific simulator details, see the appropriate section

     processor-specific simulator details, see the appropriate section

   Some configurations may include these targets as well:

   Some configurations may include these targets as well:

`target nrom DEV'

`target nrom DEV'

multi-process mode.  When the debugged program exits, or you detach

multi-process mode.  When the debugged program exits, or you detach

from it, GDB stays connected to `gdbserver' even though no program is

from it, GDB stays connected to `gdbserver' even though no program is

running.  The `run' and `attach' commands instruct `gdbserver' to run

running.  The `run' and `attach' commands instruct `gdbserver' to run

or attach to a new program.  The `run' command uses `set remote

or attach to a new program.  The `run' command uses `set remote

exec-file' (*note set remote exec-file::) to select the program to run.

exec-file' (*note set remote exec-file::) to select the program to run.

   To start `gdbserver' without supplying an initial command to run or

   To start `gdbserver' without supplying an initial command to run or

process ID to attach, use the `--multi' command line option.  Then you

process ID to attach, use the `--multi' command line option.  Then you

can connect using `target extended-remote' and start the program you

can connect using `target extended-remote' and start the program you

want to debug.

want to debug.

20.4 Remote Configuration

20.4 Remote Configuration

=========================

=========================

This section documents the configuration options available when

This section documents the configuration options available when

debugging remote programs.  For the options related to the File I/O

debugging remote programs.  For the options related to the File I/O

system.

system.

`set remoteaddresssize BITS'

`set remoteaddresssize BITS'

     Set the maximum size of address in a memory packet to the specified

     Set the maximum size of address in a memory packet to the specified

     number of bits.  GDB will mask off the address bits above that

     number of bits.  GDB will mask off the address bits above that

debugging stub.  If you need to override the autodetection, you can use

debugging stub.  If you need to override the autodetection, you can use

these commands to enable or disable individual packets.  Each packet

these commands to enable or disable individual packets.  Each packet

can be set to `on' (the remote target supports this packet), `off' (the

can be set to `on' (the remote target supports this packet), `off' (the

remote target does not support this packet), or `auto' (detect remote

remote target does not support this packet), or `auto' (detect remote

target support for this packet).  They all default to `auto'.  For more

target support for this packet).  They all default to `auto'.  For more

   During normal use, you should not have to use any of these commands.

   During normal use, you should not have to use any of these commands.

If you do, that may be a bug in your remote debugging stub, or a bug in

If you do, that may be a bug in your remote debugging stub, or a bug in

GDB.  You may want to report the problem to the GDB developers.

GDB.  You may want to report the problem to the GDB developers.