DeBUG  with GDB

                                                                                                                  
<< CONTENTS >>
          RUNNING MAN PAGES
             RUNNING 
                     Running the program.

             COMMANDS 
attach
continue
detach
finish
go
handle
interrupt
jump
kill
next
nexti
run
signal
step
stepi
target
thread
thread apply
thread disable
thread enable
tty
unset environment
until

attach
Attach to a process or file outside of GDB.
This command attaches to another target, of the same type as your last
"target" command ("info files" will show your target stack).
The command may take as argument a process id or a device file.
For a process id, you must have permission to send the process a signal,
and it must have the same effective uid as the debugger.
When using "attach" with a process id, the debugger finds the
program running in the process, looking first in the current working
directory, or (if not found there) using the source file search path
(see the "directory" command).  You can also use the "file" command
to specify the program, and to load its symbol table.

continue
Continue program being debugged, after signal or breakpoint.
If proceeding from breakpoint, a number N may be used as an argument,
which means to set the ignore count of that breakpoint to N - 1 (so that
the breakpoint won't break until the Nth time it is reached).

detach
Detach a process or file previously attached.
If a process, it is no longer traced, and it continues its execution.  If
you were debugging a file, the file is closed and gdb no longer accesses it.

finish
Execute until selected stack frame returns.
Upon return, the value returned is printed and put in the value history.

go
Usage: go <location>
Continue program being debugged, stopping at specified line or
address.
Give as argument either LINENUM or *ADDR, where ADDR is an
expression for an address to start at.
This command is a combination of tbreak and jump.

handle
Specify how to handle a signal.
Args are signals and actions to apply to those signals.
Symbolic signals (e.g. SIGSEGV) are recommended but numeric signals
from 1-15 are allowed for compatibility with old versions of GDB.
Numeric ranges may be specified with the form LOW-HIGH (e.g. 1-5).
The special arg "all" is recognized to mean all signals except those
used by the debugger, typically SIGTRAP and SIGINT.
Recognized actions include "stop", "nostop", "print", "noprint",
"pass", "nopass", "ignore", or "noignore".
Stop means reenter debugger if this signal happens (implies print).
Print means print a message if this signal happens.
Pass means let program see this signal; otherwise program doesn't know.
Ignore is a synonym for nopass and noignore is a synonym for pass.
Pass and Stop may be combined.

interrupt
Interrupt the execution of the debugged program.

jump
Continue program being debugged at specified line or address.
Give as argument either LINENUM or *ADDR, where ADDR is an expression
for an address to start at.

kill
Kill execution of program being debugged.

next
Step program, proceeding through subroutine calls.
Like the "step" command as long as subroutine calls do not happen;
when they do, the call is treated as one instruction.
Argument N means do this N times (or till program stops for another reason).

nexti
Step one instruction, but proceed through subroutine calls.
Argument N means do this N times (or till program stops for another reason).

run
Start debugged program.  You may specify arguments to give it.
Args may include "*", or "[...]"; they are expanded using "sh".
Input and output redirection with ">", "<", or ">>" are also allowed.

With no arguments, uses arguments last specified (with "run" or "set args").
To cancel previous arguments and run with no arguments,
use "set args" without arguments.

signal
Continue program giving it signal specified by the argument.
An argument of "0" means continue program without giving it a signal.

step
Step program until it reaches a different source line.
Argument N means do this N times (or till program stops for another reason).

stepi
Step one instruction exactly.
Argument N means do this N times (or till program stops for another reason).

target
Connect to a target machine or process.
The first argument is the type or protocol of the target machine.
Remaining arguments are interpreted by the target protocol.  For more
information on the arguments for a particular protocol, type
`help target ' followed by the protocol name.
Subcommands
target async -- Use a remote computer via a serial line
target child -- Unix child process (started by the "run" command)
target cisco -- Use a remote machine via TCP
target core -- Use a core file as a target
target exec -- Use an executable file as a target
target extended-async -- Use a remote computer via a serial line
target extended-remote -- Use a remote computer via a serial line
target remote -- Use a remote computer via a serial line

thread
Use this command to switch between threads.
The new thread ID must be currently known.
Subcommands
thread apply -- Apply a command to a list of threads
thread disable -- Disable a thread
thread enable -- Enable a thread from disabled list

tty
Set terminal for future runs of program being debugged.

unset
Complement to certain "set" commands
Subcommands
unset environment -- Cancel environment variable VAR for the program
unset environment
Cancel environment variable VAR for the program.
This does not affect the program until the next "run" command.

until
Execute until the program reaches a source line greater than the current
or a specified line or address or function (same args as break command).
Execution will also stop upon exit from the current stack frame.



RUNNING help page                                                              Muthukumar Kandasamy <[email protected]>


               
Hosted by www.Geocities.ws

1