| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
git-svn-id: https://www.virtualbox.org/svn/vbox/trunk@98103 cfe28804-0f27-0410-a406-dd0f0b0b656f
|
| |
|
|
|
|
| |
for GDB and the WinDbg/Kd backend, bugref:1098
git-svn-id: https://www.virtualbox.org/svn/vbox/trunk@96865 cfe28804-0f27-0410-a406-dd0f0b0b656f
|
| |
|
|
| |
git-svn-id: https://www.virtualbox.org/svn/vbox/trunk@96407 cfe28804-0f27-0410-a406-dd0f0b0b656f
|
| |
|
|
| |
git-svn-id: https://www.virtualbox.org/svn/vbox/trunk@93115 cfe28804-0f27-0410-a406-dd0f0b0b656f
|
| |
|
|
| |
git-svn-id: https://www.virtualbox.org/svn/vbox/trunk@86330 cfe28804-0f27-0410-a406-dd0f0b0b656f
|
| |
|
|
| |
git-svn-id: https://www.virtualbox.org/svn/vbox/trunk@86329 cfe28804-0f27-0410-a406-dd0f0b0b656f
|
|
|
So far TCP was the only option to communicate remotely with the internal debugger, the other option
was to use the console from the GUI directly. This commit reworks basic I/O to allow for different
providers where TCP is just one option. The second one being introduced is an IPC provider using a local
socket or named pipe depending on the platform. This allows for Windows kernel debugging over a pipe
using the KD stub in VirtualBox and WinDbg running on the host (not tested yet).
Furthermore this commit allows multiple stubs to be listening for connections at the same time, so
one can have a GDB stub listening on one TCP port and the native VBox debugger listening on another one
or even using a different I/O provider. Only one session can be active at a time though, because sharing
debugger states is impossible. To configure this the following CFGM keys need to be set for each listener:
"DBGC/<Some unique ID>/Provider" "tcp|ipc"
"DBGC/<Some unique ID>/StubType" "native|gdb|kd"
"DBGC/<Some unique ID>/Address" "<ip>|<local named pipe or socket path>"
"DBGC/<Some unique ID>/Port" "<port>" (for TCP only)
git-svn-id: https://www.virtualbox.org/svn/vbox/trunk@86327 cfe28804-0f27-0410-a406-dd0f0b0b656f
|