| /dports/www/chromium-legacy/chromium-88.0.4324.182/tools/vscode/ |
| H A D | launch.json5 | 5 "name": "Chrome Debug",
9 "program": "${workspaceRoot}/out/Debug/chrome",
32 "name": "Chrome Release",
36 "program": "${workspaceRoot}/out/Release/chrome",
45 "name": "Custom Test Debug",
49 "program": "${workspaceRoot}/out/Debug/unit_tests",
63 "name": "Attach Debug",
67 "program": "${workspaceRoot}/out/Debug/chrome",
78 "name": "Attach Android",
82 "program": "/tmp/adb-gdb-support-${env:USER}/app_process",
[all …]
|
| /dports/www/qt5-webengine/qtwebengine-everywhere-src-5.15.2/src/3rdparty/chromium/tools/vscode/ |
| H A D | launch.json5 | 5 "name": "Chrome Debug",
9 "program": "${workspaceRoot}/out/Debug/chrome",
18 "name": "Chrome Release",
22 "program": "${workspaceRoot}/out/Release/chrome",
31 "name": "Custom Test Debug",
35 "program": "${workspaceRoot}/out/Debug/unit_tests",
47 "name": "Attach Debug",
51 "program": "${workspaceRoot}/out/Debug/chrome",
60 "name": "Attach Android",
64 "program": "/tmp/adb-gdb-support-${env:USER}/app_process",
[all …]
|
| /dports/dns/bind9-devel/bind9-e112afa15668bd3b1baed59df2d21e01b46da15e/bin/dnssec/ |
| H A D | dnssec-verify.c | 66 const char *program = "dnssec-verify"; variable
99 dns_name_t *name; in loadzone() local
106 name = dns_fixedname_initname(&fname); in loadzone()
107 result = dns_name_fromtext(name, &b, dns_rootname, 0, NULL); in loadzone()
113 result = dns_db_create(mctx, "rbt", name, dns_dbtype_zone, rdclass, 0, in loadzone()
146 fprintf(stderr, "\t%s [options] zonefile [keys]\n", program); in usage()
257 program, isc_commandline_option); in main()
267 version(program); in main()
270 fprintf(stderr, "%s: unhandled option -%c\n", program, in main()
317 gdb = NULL; in main()
[all …]
|
| /dports/dns/samba-nsupdate/bind-9.16.5/bin/dnssec/ |
| H A D | dnssec-verify.c | 69 const char *program = "dnssec-verify"; variable
99 dns_name_t *name; in loadzone() local
106 name = dns_fixedname_initname(&fname); in loadzone()
107 result = dns_name_fromtext(name, &b, dns_rootname, 0, NULL); in loadzone()
113 result = dns_db_create(mctx, "rbt", name, dns_dbtype_zone, rdclass, 0, in loadzone()
146 fprintf(stderr, "\t%s [options] zonefile [keys]\n", program); in usage()
275 program, isc_commandline_option); in main()
285 version(program); in main()
288 fprintf(stderr, "%s: unhandled option -%c\n", program, in main()
335 gdb = NULL; in main()
[all …]
|
| /dports/dns/bind916/bind-9.16.27/bin/dnssec/ |
| H A D | dnssec-verify.c | 71 const char *program = "dnssec-verify"; variable
104 dns_name_t *name; in loadzone() local
111 name = dns_fixedname_initname(&fname); in loadzone()
112 result = dns_name_fromtext(name, &b, dns_rootname, 0, NULL); in loadzone()
118 result = dns_db_create(mctx, "rbt", name, dns_dbtype_zone, rdclass, 0, in loadzone()
151 fprintf(stderr, "\t%s [options] zonefile [keys]\n", program); in usage()
280 program, isc_commandline_option); in main()
290 version(program); in main()
293 fprintf(stderr, "%s: unhandled option -%c\n", program, in main()
340 gdb = NULL; in main()
[all …]
|
| /dports/dns/bind911/bind-9.11.37/bin/dnssec/ |
| H A D | dnssec-verify.c | 72 const char *program = "dnssec-verify"; variable
94 dns_name_t *name; in loadzone() local
101 name = dns_fixedname_initname(&fname); in loadzone()
102 result = dns_name_fromtext(name, &b, dns_rootname, 0, NULL); in loadzone()
107 result = dns_db_create(mctx, "rbt", name, dns_dbtype_zone, in loadzone()
140 fprintf(stderr, "\t%s [options] zonefile [keys]\n", program); in usage()
263 program, isc_commandline_option); in main()
272 version(program); in main()
276 program, isc_commandline_option); in main()
325 gdb = NULL; in main()
[all …]
|
| /dports/dns/bind-tools/bind-9.16.27/bin/dnssec/ |
| H A D | dnssec-verify.c | 71 const char *program = "dnssec-verify"; variable
104 dns_name_t *name; in loadzone() local
111 name = dns_fixedname_initname(&fname); in loadzone()
112 result = dns_name_fromtext(name, &b, dns_rootname, 0, NULL); in loadzone()
118 result = dns_db_create(mctx, "rbt", name, dns_dbtype_zone, rdclass, 0, in loadzone()
151 fprintf(stderr, "\t%s [options] zonefile [keys]\n", program); in usage()
280 program, isc_commandline_option); in main()
290 version(program); in main()
293 fprintf(stderr, "%s: unhandled option -%c\n", program, in main()
340 gdb = NULL; in main()
[all …]
|
| /dports/news/husky-areafix/husky-areafix-1.9.20191207/huskybse/develop-docs/ |
| H A D | segfault | 8 fault" type error in a Husky program. It describes how than can use gdb to
89 before the failing program is called. Also note that this only works in
96 Once you have found the core file, you can type "gdb <name-of-program> <name
127 (gdb)
138 Now, at the (gdb) prompt, type (gdb) where:
143 (gdb)
149 see the function name (testfn), file name (test.c) and line number (3) where
170 don't recreate the crash, but load the program into gdb without supplying a
193 (gdb) run
194 Starting program: /home/tobi/bin/hpt toss
[all …]
|
| /dports/news/husky/husky-1.9.20191207/huskybse/develop-docs/ |
| H A D | segfault | 8 fault" type error in a Husky program. It describes how than can use gdb to
89 before the failing program is called. Also note that this only works in
96 Once you have found the core file, you can type "gdb <name-of-program> <name
127 (gdb)
138 Now, at the (gdb) prompt, type (gdb) where:
143 (gdb)
149 see the function name (testfn), file name (test.c) and line number (3) where
170 don't recreate the crash, but load the program into gdb without supplying a
193 (gdb) run
194 Starting program: /home/tobi/bin/hpt toss
[all …]
|
| /dports/news/husky-fidoconf/husky-fidoconf-1.9.20191207/huskybse/develop-docs/ |
| H A D | segfault | 8 fault" type error in a Husky program. It describes how than can use gdb to
89 before the failing program is called. Also note that this only works in
96 Once you have found the core file, you can type "gdb <name-of-program> <name
127 (gdb)
138 Now, at the (gdb) prompt, type (gdb) where:
143 (gdb)
149 see the function name (testfn), file name (test.c) and line number (3) where
170 don't recreate the crash, but load the program into gdb without supplying a
193 (gdb) run
194 Starting program: /home/tobi/bin/hpt toss
[all …]
|
| /dports/news/husky-sqpack/husky-sqpack-1.9.20191207/huskybse/develop-docs/ |
| H A D | segfault | 8 fault" type error in a Husky program. It describes how than can use gdb to
89 before the failing program is called. Also note that this only works in
96 Once you have found the core file, you can type "gdb <name-of-program> <name
127 (gdb)
138 Now, at the (gdb) prompt, type (gdb) where:
143 (gdb)
149 see the function name (testfn), file name (test.c) and line number (3) where
170 don't recreate the crash, but load the program into gdb without supplying a
193 (gdb) run
194 Starting program: /home/tobi/bin/hpt toss
[all …]
|
| /dports/news/husky-hpt/husky-hpt-1.9.20191207/huskybse/develop-docs/ |
| H A D | segfault | 8 fault" type error in a Husky program. It describes how than can use gdb to
89 before the failing program is called. Also note that this only works in
96 Once you have found the core file, you can type "gdb <name-of-program> <name
127 (gdb)
138 Now, at the (gdb) prompt, type (gdb) where:
143 (gdb)
149 see the function name (testfn), file name (test.c) and line number (3) where
170 don't recreate the crash, but load the program into gdb without supplying a
193 (gdb) run
194 Starting program: /home/tobi/bin/hpt toss
[all …]
|
| /dports/news/husky-smapi/husky-smapi-1.9.20191207,1/huskybse/develop-docs/ |
| H A D | segfault | 8 fault" type error in a Husky program. It describes how than can use gdb to
89 before the failing program is called. Also note that this only works in
96 Once you have found the core file, you can type "gdb <name-of-program> <name
127 (gdb)
138 Now, at the (gdb) prompt, type (gdb) where:
143 (gdb)
149 see the function name (testfn), file name (test.c) and line number (3) where
170 don't recreate the crash, but load the program into gdb without supplying a
193 (gdb) run
194 Starting program: /home/tobi/bin/hpt toss
[all …]
|
| /dports/news/husky-huskylib/husky-huskylib-1.9.20191207/huskybse/develop-docs/ |
| H A D | segfault | 8 fault" type error in a Husky program. It describes how than can use gdb to
89 before the failing program is called. Also note that this only works in
96 Once you have found the core file, you can type "gdb <name-of-program> <name
127 (gdb)
138 Now, at the (gdb) prompt, type (gdb) where:
143 (gdb)
149 see the function name (testfn), file name (test.c) and line number (3) where
170 don't recreate the crash, but load the program into gdb without supplying a
193 (gdb) run
194 Starting program: /home/tobi/bin/hpt toss
[all …]
|
| /dports/news/husky-htick/husky-htick-1.9.20191207/huskybse/develop-docs/ |
| H A D | segfault | 8 fault" type error in a Husky program. It describes how than can use gdb to
89 before the failing program is called. Also note that this only works in
96 Once you have found the core file, you can type "gdb <name-of-program> <name
127 (gdb)
138 Now, at the (gdb) prompt, type (gdb) where:
143 (gdb)
149 see the function name (testfn), file name (test.c) and line number (3) where
170 don't recreate the crash, but load the program into gdb without supplying a
193 (gdb) run
194 Starting program: /home/tobi/bin/hpt toss
[all …]
|
| /dports/editors/libreoffice/libreoffice-7.2.6.2/.vscode/ |
| H A D | vs-code-template.code-workspace.in | 12 "name": "srcdir",
16 "name": "builddir",
123 "program": "@INSTROOT@/program/soffice.bin",
132 "name": "SAL_LOG_DISABLED",
137 "MIMode": "gdb",
149 "program": "@INSTROOT@/MacOS/soffice",
165 "name": "run in gdb with clear userprofile",
169 "program": "@INSTROOT@/program/soffice.bin",
177 "name": "SAL_LOG_DISABLED",
182 "MIMode": "gdb",
[all …]
|
| /dports/sysutils/uefi-edk2-bhyve-csm/uefi-edk2-aa8d718/EmulatorPkg/Unix/ |
| H A D | GdbRun | 6 # This program and the accompanying materials
24 # changed from the value we pre-initialized it to. If so, the program
25 # had exited, so gdb should now quit.
31 source Host.gdb
36 # We keep track of the number of symbol files we have loaded via gdb
42 # This macro adds a symbols file for gdb
45 # @param $arg1 - Symbol file name
56 # This macro removes a symbols file for gdb
59 # @param $arg1 - Symbol file name
71 # in Xcode the program is already runing. Issuing a run command
[all …]
|
| /dports/devel/zpu-binutils/zpu-toolchain-1.0/toolchain/gdb/gdb/doc/ |
| H A D | gdb.info-2 | 855 GDB needs to know the file name of the program to be debugged, both in
1787 GDB as usual, using the name of the local copy of your program as the
1891 the name of your program; and the arguments for your program. The
1971 the name of your program; and the arguments for your program. The
2587 some cases there will be name clashes within a program (particularly if
2951 is connected, you can start up GDB. Call `gdb' with the name of your
3104 To run a program on the board, start up `gdb' with the name of
4857 If you specify an absolute file name when prompted for the `M-x gdb'
4859 program resides. If you only specify the file name, then Emacs sets
4872 By default, `M-x gdb' calls the program called `gdb'. If you need
[all …]
|
| /dports/devel/zpu-gcc/zpu-toolchain-1.0/toolchain/gdb/gdb/doc/ |
| H A D | gdb.info-2 | 855 GDB needs to know the file name of the program to be debugged, both in
1787 GDB as usual, using the name of the local copy of your program as the
1891 the name of your program; and the arguments for your program. The
1971 the name of your program; and the arguments for your program. The
2587 some cases there will be name clashes within a program (particularly if
2951 is connected, you can start up GDB. Call `gdb' with the name of your
3104 To run a program on the board, start up `gdb' with the name of
4857 If you specify an absolute file name when prompted for the `M-x gdb'
4859 program resides. If you only specify the file name, then Emacs sets
4872 By default, `M-x gdb' calls the program called `gdb'. If you need
[all …]
|
| /dports/devel/wasi-libcxx/llvm-project-13.0.1.src/lldb/docs/man/ |
| H A D | lldb-server.rst | 36 Runs the server using the gdb-remote protocol. LLDB can afterwards
37 connect to the server using *gdb-remote* command.
63 .. option:: --named-pipe <name>
99 .. option:: --attach <pid-or-name>
101 Attach to the process given by a (numeric) process id or a name.
157 Specify the range of ports that can be used for gdb-server connections. Both
185 identifier or name. The process will be stopped immediately after starting
190 lldb-server g :1234 --attach program-name
192 Use *gdb-remote* command to connect to the server:
194 (lldb) gdb-remote 1234
[all …]
|
| /dports/devel/llvm12/llvm-project-12.0.1.src/lldb/docs/man/ |
| H A D | lldb-server.rst | 36 Runs the server using the gdb-remote protocol. LLDB can afterwards
37 connect to the server using *gdb-remote* command.
63 .. option:: --named-pipe <name>
99 .. option:: --attach <pid-or-name>
101 Attach to the process given by a (numeric) process id or a name.
157 Specify the range of ports that can be used for gdb-server connections. Both
185 identifier or name. The process will be stopped immediately after starting
190 lldb-server g :1234 --attach program-name
192 Use *gdb-remote* command to connect to the server:
194 (lldb) gdb-remote 1234
[all …]
|
| /dports/lang/rust/rustc-1.58.1-src/src/llvm-project/lldb/docs/man/ |
| H A D | lldb-server.rst | 36 Runs the server using the gdb-remote protocol. LLDB can afterwards
37 connect to the server using *gdb-remote* command.
63 .. option:: --named-pipe <name>
99 .. option:: --attach <pid-or-name>
101 Attach to the process given by a (numeric) process id or a name.
157 Specify the range of ports that can be used for gdb-server connections. Both
185 identifier or name. The process will be stopped immediately after starting
190 lldb-server g :1234 --attach program-name
192 Use *gdb-remote* command to connect to the server:
194 (lldb) gdb-remote 1234
[all …]
|
| /dports/devel/llvm-devel/llvm-project-f05c95f10fc1d8171071735af8ad3a9e87633120/lldb/docs/man/ |
| H A D | lldb-server.rst | 36 Runs the server using the gdb-remote protocol. LLDB can afterwards
37 connect to the server using *gdb-remote* command.
63 .. option:: --named-pipe <name>
99 .. option:: --attach <pid-or-name>
101 Attach to the process given by a (numeric) process id or a name.
157 Specify the range of ports that can be used for gdb-server connections. Both
185 identifier or name. The process will be stopped immediately after starting
190 lldb-server g :1234 --attach program-name
192 Use *gdb-remote* command to connect to the server:
194 (lldb) gdb-remote 1234
[all …]
|
| /dports/devel/wasi-compiler-rt13/llvm-project-13.0.1.src/lldb/docs/man/ |
| H A D | lldb-server.rst | 36 Runs the server using the gdb-remote protocol. LLDB can afterwards
37 connect to the server using *gdb-remote* command.
63 .. option:: --named-pipe <name>
99 .. option:: --attach <pid-or-name>
101 Attach to the process given by a (numeric) process id or a name.
157 Specify the range of ports that can be used for gdb-server connections. Both
185 identifier or name. The process will be stopped immediately after starting
190 lldb-server g :1234 --attach program-name
192 Use *gdb-remote* command to connect to the server:
194 (lldb) gdb-remote 1234
[all …]
|
| /dports/devel/wasi-compiler-rt12/llvm-project-12.0.1.src/lldb/docs/man/ |
| H A D | lldb-server.rst | 36 Runs the server using the gdb-remote protocol. LLDB can afterwards
37 connect to the server using *gdb-remote* command.
63 .. option:: --named-pipe <name>
99 .. option:: --attach <pid-or-name>
101 Attach to the process given by a (numeric) process id or a name.
157 Specify the range of ports that can be used for gdb-server connections. Both
185 identifier or name. The process will be stopped immediately after starting
190 lldb-server g :1234 --attach program-name
192 Use *gdb-remote* command to connect to the server:
194 (lldb) gdb-remote 1234
[all …]
|