Translations by Anthony Harrington
Anthony Harrington has submitted the following strings to this translation. Contributions are visually coded: currently used translations, unreviewed suggestions, rejected suggestions.
| 1 → 12 of 12 results | First • Previous • Next • Last |
| 1153. |
cannot parse task id '%s'
|
|
| 2022-04-13 |
cannot parse task ID '%s'
|
|
| 1373. |
Unrecognized DWARF opcode 0x%02x at %ld
|
|
| 2012-08-05 |
Unrecognised DWARF opcode 0x%02x at %ld
|
|
| 1712. |
Got a strange event, msg id = %d.
|
|
| 2022-04-13 |
Got a strange event, msg ID = %d.
|
|
| 1719. |
Can't run single thread id %s: no such thread!
|
|
| 2022-04-13 |
Can't run single thread ID %s: no such thread!
|
|
| 1720. |
Can't step thread id %s: no such thread.
|
|
| 2022-04-13 |
Can't step thread ID %s: no such thread.
|
|
| 1930. |
The program being debugged was signaled while in a function called from GDB.
GDB remains in the frame where the signal was received.
To change this behavior use "set unwindonsignal on".
Evaluation of the expression containing the function
(%s) will be abandoned.
When the function is done executing, GDB will silently stop.
|
|
| 2022-04-13 |
The program being debugged was signalled while in a function called from GDB.
GDB remains in the frame where the signal was received.
To change this behaviour use "set unwindonsignal on".
Evaluation of the expression containing the function
(%s) will be abandoned.
When the function is done executing, GDB will silently stop.
|
|
| 2014. |
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.
|
|
| 2022-04-13 |
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.
|
|
| 2118. |
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 "s" (toggles between stop and nostop),
"r" (toggles between print and noprint), "i" (toggles between pass and nopass), "Q" (noprint)
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.
|
|
| 2012-08-05 |
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 recognised to mean all signals except those
used by the debugger, typically SIGTRAP and SIGINT.
Recognised actions include "s" (toggles between stop and nostop),
"r" (toggles between print and noprint), "i" (toggles between pass and nopass), "Q" (noprint)
Stop means re-enter 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.
|
|
| 2012-08-05 |
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 recognised to mean all signals except those
used by the debugger, typically SIGTRAP and SIGINT.
Recognized actions include "s" (toggles between stop and nostop),
"r" (toggles between print and noprint), "i" (toggles between pass and nopass), "Q" (noprint)
Stop means re-enter 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.
|
|
| 2255. |
Requires argument (checkpoint id to delete)
|
|
| 2022-04-13 |
Requires argument (checkpoint ID to delete)
|
|
| 2261. |
Requires argument (checkpoint id to detach)
|
|
| 2022-04-13 |
Requires argument (checkpoint ID to detach)
|
|
| 2276. |
Requires argument (checkpoint id to restart)
|
|
| 2022-04-13 |
Requires argument (checkpoint ID to restart)
|
|
