| /dports/devel/valgrind-lts/valgrind-dragonfly-dragonfly/coregrind/m_gdbserver/ |
| H A D | README_DEVELOPERS | 11 gdb debugger typically is used to debug a process running
13 to fetch data from the process being debugged
14 or to change data in the process
15 or interrupt the process
34 to allow gdb to remotely debug process running on a linux or MacOS or
49 server: there is a "if gdbserver is active" check in the translate
99 process is stopped, and re-inserts all breaks when the process
135 called vgdb is needed between gdb and the valgrind-ified process.
166 code inside the valgrind process.
204 process using gdbserver.
[all …]
|
| /dports/devel/valgrind/valgrind-dragonfly-dragonfly/coregrind/m_gdbserver/ |
| H A D | README_DEVELOPERS | 11 gdb debugger typically is used to debug a process running
13 to fetch data from the process being debugged
14 or to change data in the process
15 or interrupt the process
34 to allow gdb to remotely debug process running on a linux or MacOS or
49 server: there is a "if gdbserver is active" check in the translate
99 process is stopped, and re-inserts all breaks when the process
135 called vgdb is needed between gdb and the valgrind-ified process.
166 code inside the valgrind process.
204 process using gdbserver.
[all …]
|
| /dports/audio/sdl2_mixer/SDL2_mixer-2.0.4/external/mpg123-1.25.6/ |
| H A D | TODO | 10 0. Fix that ugly crash that happens sometimes when Ctrl+C-ing with jack output active:
13 [New process 6293]
14 [New process 6291]
15 [New process 6292]
16 [New process 6284]
18 (gdb) bt
|
| /dports/devel/kdevelop/kdevelop-21.12.3/po/el/ |
| H A D | kdevgdb.po | 877 #~ "<b>Attach to process</b><p>Attaches the debugger to a running process.</p>"
925 #~ msgid "Debug process %1"
928 #~ msgid "Attach to a process"
1481 #~ msgctxt "process status"
1487 #~ msgctxt "process status"
1534 #~ msgctxt "process heading"
1540 #~ msgctxt "process heading"
1546 #~ msgctxt "process heading"
1596 #~| "list showing what function is currently active and who called each "
1601 #~ "list showing which function is currently active, and what called each "
[all …]
|
| H A D | kdevdebuggercommon.po | 178 #| "<b>Attach to process</b><p>Attaches the debugger to a running process.</p>"
181 "<b>Attach to process</b><p>Attaches the debugger to a running process.</p>"
280 msgid "Debug process %1"
806 #~ msgid "Attach to process"
1004 #~| "remote process.\n"
1548 #~ msgctxt "process status"
1554 #~ msgctxt "process status"
1596 #~ msgctxt "process heading"
1658 #~| "list showing what function is currently active and who called each "
1663 #~ "list showing which function is currently active, and what called each "
[all …]
|
| /dports/audio/mpg123/mpg123-1.29.3/ |
| H A D | TODO | 5 0. Fix that ugly crash that happens sometimes when Ctrl+C-ing with jack output active:
8 [New process 6293]
9 [New process 6291]
10 [New process 6292]
11 [New process 6284]
13 (gdb) bt
|
| /dports/devel/kdevelop/kdevelop-21.12.3/po/en_GB/ |
| H A D | kdevgdb.po | 756 #~ "<b>Attach to process</b><p>Attaches the debugger to a running process.</p>"
758 #~ "<b>Attach to process</b><p>Attaches the debugger to a running process.</p>"
801 #~ msgid "Debug process %1"
802 #~ msgstr "Debug process %1"
1377 #~ msgctxt "process status"
1383 #~ msgctxt "process status"
1430 #~ msgctxt "process heading"
1493 #~ "list showing which function is currently active, and what called each "
1498 #~ "list showing which function is currently active, and what called each "
1505 #~ msgid "Breakpoint is active"
[all …]
|
| H A D | kdevdebuggercommon.po | 162 "<b>Attach to process</b><p>Attaches the debugger to a running process.</p>"
164 "<b>Attach to process</b><p>Attaches the debugger to a running process.</p>"
250 msgid "Debug process %1"
251 msgstr "Debug process %1"
725 #~ msgid "Attach to process"
1454 #~ msgctxt "process status"
1460 #~ msgctxt "process status"
1565 #~ "list showing which function is currently active, and what called each "
1570 #~ "list showing which function is currently active, and what called each "
1577 #~ msgid "Breakpoint is active"
[all …]
|
| /dports/devel/kdevelop/kdevelop-21.12.3/po/nl/ |
| H A D | kdevgdb.po | 779 #~ msgid "Attach to process..."
783 #~ "<b>Attach to process</b><p>Attaches the debugger to a running process.</p>"
829 #~ msgid "Debug process %1"
836 #~ msgid "Attach to a process"
1338 #~ msgctxt "process status"
1344 #~ msgctxt "process status"
1380 #~ msgctxt "process heading"
1386 #~ msgctxt "process heading"
1430 #~| "list showing what function is currently active and who called each "
1435 #~ "list showing which function is currently active, and what called each "
[all …]
|
| /dports/devel/gdb761/gdb-7.6.1/gdb/doc/ |
| H A D | gdb.info-4 | 984 Gives the current process or thread number. When no process is
1048 Scroll the active window one page up.
1051 Scroll the active window one page down.
1054 Scroll the active window one line up.
1057 Scroll the active window one line down.
1060 Scroll the active window one column left.
1063 Scroll the active window one column right.
1161 Make the next window active for scrolling.
1230 `set tui active-border-mode MODE'
1610 additional `--process' option, nor an notion of the current process in
[all …]
|
| /dports/devel/kdevelop/kdevelop-21.12.3/po/nds/ |
| H A D | kdevdebuggercommon.po | 25 #| msgid "Attach to a process"
176 #| "<b>Attach to process</b><p>Attaches the debugger to a running process.</p>"
179 "<b>Attach to process</b><p>Attaches the debugger to a running process.</p>"
276 msgid "Debug process %1"
796 #~ msgid "Attach to process"
997 #~| "remote process.\n"
1506 #~ msgctxt "process status"
1512 #~ msgctxt "process status"
1554 #~ msgctxt "process heading"
1614 #~ "list showing which function is currently active, and what called each "
[all …]
|
| H A D | kdevgdb.po | 403 #| "remote process.\n"
845 #~ "<b>Attach to process</b><p>Attaches the debugger to a running process.</p>"
893 #~ msgid "Debug process %1"
896 #~ msgid "Attach to a process"
1424 #~ msgctxt "process status"
1430 #~ msgctxt "process status"
1477 #~ msgctxt "process heading"
1483 #~ msgctxt "process heading"
1489 #~ msgctxt "process heading"
1537 #~ "list showing which function is currently active, and what called each "
[all …]
|
| /dports/devel/kdevelop/kdevelop-21.12.3/po/pl/ |
| H A D | kdevgdb.po | 788 #~ msgid "Attach to process..."
792 #~ "<b>Attach to process</b><p>Attaches the debugger to a running process.</p>"
839 #~ msgid "Debug process %1"
846 #~ msgid "Attach to a process"
1400 #~ msgctxt "process status"
1405 #~ msgctxt "process status"
1449 #~ msgctxt "process heading"
1455 #~ msgctxt "process heading"
1503 #~| "list showing what function is currently active and who called each "
1508 #~ "list showing which function is currently active, and what called each "
[all …]
|
| H A D | kdevdebuggercommon.po | 177 "<b>Attach to process</b><p>Attaches the debugger to a running process.</p>"
267 msgid "Debug process %1"
277 msgid "Attaching to process %1"
748 #~ msgid "Attach to process"
1464 #~ msgctxt "process status"
1469 #~ msgctxt "process status"
1508 #~ msgctxt "process heading"
1514 #~ msgctxt "process heading"
1562 #~| "list showing what function is currently active and who called each "
1567 #~ "list showing which function is currently active, and what called each "
[all …]
|
| /dports/sysutils/bareos19-traymonitor/bareos-Release-19.2.11/docs/manuals/source/Appendix/ |
| H A D | Debugging.rst | 24 #. On Linux, :command:`gdb` (the GNU debugger) must be installed. On some systems such as Solaris, …
45 :caption: get the process ID of a running Bareos daemon
62 …ce a similar backtrace on systems other than Linux, either using :command:`gdb` or some other debu…
63 …to invoke the correct debugger, and possibly correct the :file:`btraceback.gdb` script to have app…
79 bareos@host:~# gdb --args /usr/sbin/bareos-sd -f -s -d 200
80 (gdb) run
99 #. When Bareos crashes, the gdb shell window will become active and gdb will show you the error tha…
106 (gdb) thread apply all bt
|
| /dports/sysutils/bareos19-client/bareos-Release-19.2.11/docs/manuals/source/Appendix/ |
| H A D | Debugging.rst | 24 #. On Linux, :command:`gdb` (the GNU debugger) must be installed. On some systems such as Solaris, …
45 :caption: get the process ID of a running Bareos daemon
62 …ce a similar backtrace on systems other than Linux, either using :command:`gdb` or some other debu…
63 …to invoke the correct debugger, and possibly correct the :file:`btraceback.gdb` script to have app…
79 bareos@host:~# gdb --args /usr/sbin/bareos-sd -f -s -d 200
80 (gdb) run
99 #. When Bareos crashes, the gdb shell window will become active and gdb will show you the error tha…
106 (gdb) thread apply all bt
|
| /dports/sysutils/bareos-client/bareos-Release-20.0.3/docs/manuals/source/Appendix/ |
| H A D | Debugging.rst | 24 #. On Linux, :command:`gdb` (the GNU debugger) must be installed. On some systems such as Solaris, …
45 :caption: get the process ID of a running Bareos daemon
62 …ce a similar backtrace on systems other than Linux, either using :command:`gdb` or some other debu…
63 …to invoke the correct debugger, and possibly correct the :file:`btraceback.gdb` script to have app…
79 bareos@host:~# gdb --args /usr/sbin/bareos-sd -f -s -d 200
80 (gdb) run
99 #. When Bareos crashes, the gdb shell window will become active and gdb will show you the error tha…
106 (gdb) thread apply all bt
|
| /dports/sysutils/bareos18-traymonitor/bareos-Release-18.2.12/docs/manuals/source/Appendix/ |
| H A D | Debugging.rst | 24 #. On Linux, :command:`gdb` (the GNU debugger) must be installed. On some systems such as Solaris, …
45 :caption: get the process ID of a running Bareos daemon
62 …gdb` or some other debugger. Solaris:index:`\ <single: Platform; Solaris; Debug>`\ with :command:…
77 <command>gdb</command><parameter> --args /usr/sbin/bareos-sd -f -s -d 200</parameter>
78 (gdb) <input>run</input>
97 #. When Bareos crashes, the gdb shell window will become active and gdb will show you the error tha…
104 (gdb) <input>thread apply all bt</input>
|
| /dports/sysutils/bareos-traymonitor/bareos-Release-20.0.3/docs/manuals/source/Appendix/ |
| H A D | Debugging.rst | 24 #. On Linux, :command:`gdb` (the GNU debugger) must be installed. On some systems such as Solaris, …
45 :caption: get the process ID of a running Bareos daemon
62 …ce a similar backtrace on systems other than Linux, either using :command:`gdb` or some other debu…
63 …to invoke the correct debugger, and possibly correct the :file:`btraceback.gdb` script to have app…
79 bareos@host:~# gdb --args /usr/sbin/bareos-sd -f -s -d 200
80 (gdb) run
99 #. When Bareos crashes, the gdb shell window will become active and gdb will show you the error tha…
106 (gdb) thread apply all bt
|
| /dports/sysutils/bareos-server/bareos-Release-20.0.3/docs/manuals/source/Appendix/ |
| H A D | Debugging.rst | 24 #. On Linux, :command:`gdb` (the GNU debugger) must be installed. On some systems such as Solaris, …
45 :caption: get the process ID of a running Bareos daemon
62 …ce a similar backtrace on systems other than Linux, either using :command:`gdb` or some other debu…
63 …to invoke the correct debugger, and possibly correct the :file:`btraceback.gdb` script to have app…
79 bareos@host:~# gdb --args /usr/sbin/bareos-sd -f -s -d 200
80 (gdb) run
99 #. When Bareos crashes, the gdb shell window will become active and gdb will show you the error tha…
106 (gdb) thread apply all bt
|
| /dports/sysutils/bareos18-server/bareos-Release-18.2.12/docs/manuals/source/Appendix/ |
| H A D | Debugging.rst | 24 #. On Linux, :command:`gdb` (the GNU debugger) must be installed. On some systems such as Solaris, …
45 :caption: get the process ID of a running Bareos daemon
62 …gdb` or some other debugger. Solaris:index:`\ <single: Platform; Solaris; Debug>`\ with :command:…
77 <command>gdb</command><parameter> --args /usr/sbin/bareos-sd -f -s -d 200</parameter>
78 (gdb) <input>run</input>
97 #. When Bareos crashes, the gdb shell window will become active and gdb will show you the error tha…
104 (gdb) <input>thread apply all bt</input>
|
| /dports/sysutils/bareos18-client/bareos-Release-18.2.12/docs/manuals/source/Appendix/ |
| H A D | Debugging.rst | 24 #. On Linux, :command:`gdb` (the GNU debugger) must be installed. On some systems such as Solaris, …
45 :caption: get the process ID of a running Bareos daemon
62 …gdb` or some other debugger. Solaris:index:`\ <single: Platform; Solaris; Debug>`\ with :command:…
77 <command>gdb</command><parameter> --args /usr/sbin/bareos-sd -f -s -d 200</parameter>
78 (gdb) <input>run</input>
97 #. When Bareos crashes, the gdb shell window will become active and gdb will show you the error tha…
104 (gdb) <input>thread apply all bt</input>
|
| /dports/sysutils/bareos19-server/bareos-Release-19.2.11/docs/manuals/source/Appendix/ |
| H A D | Debugging.rst | 24 #. On Linux, :command:`gdb` (the GNU debugger) must be installed. On some systems such as Solaris, …
45 :caption: get the process ID of a running Bareos daemon
62 …ce a similar backtrace on systems other than Linux, either using :command:`gdb` or some other debu…
63 …to invoke the correct debugger, and possibly correct the :file:`btraceback.gdb` script to have app…
79 bareos@host:~# gdb --args /usr/sbin/bareos-sd -f -s -d 200
80 (gdb) run
99 #. When Bareos crashes, the gdb shell window will become active and gdb will show you the error tha…
106 (gdb) thread apply all bt
|
| /dports/www/bareos-webui/bareos-Release-20.0.3/docs/manuals/source/Appendix/ |
| H A D | Debugging.rst | 24 #. On Linux, :command:`gdb` (the GNU debugger) must be installed. On some systems such as Solaris, …
45 :caption: get the process ID of a running Bareos daemon
62 …ce a similar backtrace on systems other than Linux, either using :command:`gdb` or some other debu…
63 …to invoke the correct debugger, and possibly correct the :file:`btraceback.gdb` script to have app…
79 bareos@host:~# gdb --args /usr/sbin/bareos-sd -f -s -d 200
80 (gdb) run
99 #. When Bareos crashes, the gdb shell window will become active and gdb will show you the error tha…
106 (gdb) thread apply all bt
|
| /dports/www/bareos18-webui/bareos-Release-18.2.12/docs/manuals/source/Appendix/ |
| H A D | Debugging.rst | 24 #. On Linux, :command:`gdb` (the GNU debugger) must be installed. On some systems such as Solaris, …
45 :caption: get the process ID of a running Bareos daemon
62 …gdb` or some other debugger. Solaris:index:`\ <single: Platform; Solaris; Debug>`\ with :command:…
77 <command>gdb</command><parameter> --args /usr/sbin/bareos-sd -f -s -d 200</parameter>
78 (gdb) <input>run</input>
97 #. When Bareos crashes, the gdb shell window will become active and gdb will show you the error tha…
104 (gdb) <input>thread apply all bt</input>
|