Next: , Previous: File Transfer, Up: Remote Debugging

20.3 Using the gdbserver Program

The following operators are supported, and appear in order of increasing precedence:

,
Function argument or array index separator.
:=
Assignment. The value of var := value is value.
<, >
Less than, greater than on integral, floating-point, or enumerated types.
<=, >=
Less than or equal to, greater than or equal to on integral, floating-point and enumerated types, or set inclusion on set types. Same precedence as <.
=, <>, #
Equality and two ways of expressing inequality, valid on scalar types. Same precedence as <. In gdb scripts, only <> is available for inequality, since # conflicts with the script comment character.
IN
Set membership. Defined on set types and the types of their members. Same precedence as <.
OR
Boolean disjunction. Defined on boolean types.
AND, &
Boolean conjunction. Defined on boolean types.
@
The gdb “artificial array” operator (see Expressions).
+, -
Addition and subtraction on integral and floating-point types, or union and difference on set types.
*
Multiplication on integral and floating-point types, or set intersection on set types.
/
Division on floating-point types, or symmetric set difference on set types. Same precedence as *.
DIV, MOD
Integer division and remainder. Defined on integral types. Same precedence as *.
-
Negative. Defined on INTEGER and REAL data.
^
Pointer dereferencing. Defined on pointer types.
NOT
Boolean negation. Defined on boolean types. Same precedence as ^.
.
RECORD field selector. Defined on RECORD data. Same precedence as ^.
[]
Array indexing. Defined on ARRAY data. Same precedence as ^.
()
Procedure argument list. Defined on PROCEDURE objects. Same precedence as ^.
::, .
gdb and Modula-2 scope operators.
Warning: Set expressions and their operations are not yet supported, so gdb treats the use of the operator IN, or the use of operators +, -, *, /, =, , <>, #, <=, and >= on sets as an error.
./usr/share/doc/gdb-doc/html/gdb/Thread-Stops.html0000644000000000000000000000722311350760301020573 0ustar rootroot Thread Stops - Debugging with GDB

Previous: Signals, Up: Stopping

5.4 Stopping and Starting Multi-thread Programs

gdb supports debugging programs with multiple threads (see Debugging Programs with Multiple Threads). There are two modes of controlling execution of your program within the debugger. In the default mode, referred to as all-stop mode, when any thread in your program stops (for example, at a breakpoint or while being stepped), all other threads in the program are also stopped by gdb. On some targets, gdb also supports non-stop mode, in which other threads can continue to run freely while you examine the stopped thread in the debugger.

./usr/share/doc/gdb-doc/html/gdb/Readline-Killing-Commands.html0000644000000000000000000001075111350760301023127 0ustar rootroot Readline Killing Commands - Debugging with GDB

Next: , Previous: Readline Movement Commands, Up: Readline Interaction

31.2.3 Readline Killing Commands

Killing text means to delete the text from the line, but to save it away for later use, usually by yanking (re-inserting) it back into the line. (`Cut' and `paste' are more recent jargon for `kill' and `yank'.)

If the description for a command says that it `kills' text, then you can be sure that you can get the text back in a different (or the same) place later.

When you use a kill command, the text is saved in a kill-ring. Any number of consecutive kills save all of the killed text together, so that when you yank it back, you get it all. The kill ring is not line specific; the text that you killed on a previously typed lin