If i run : winedbg --gdb --no-start test.exe
it say : target remote localhost:55304
But if I run it second time , it say a different port , for example target remote localhost:111111
is there a command line argument for winedbg so it to listen to same port every time , and to do not change the port ,so I can specity to witch port it to listen , or I have to recompile winedbg ? Thank you!
On Wed, Oct 19, 2016 at 1:07 PM, A B dianaxxyyzz@gmail.com wrote:
If i run : winedbg --gdb --no-start test.exe
it say : target remote localhost:55304
But if I run it second time , it say a different port , for example target remote localhost:111111
is there a command line argument for winedbg so it to listen to same port every time , and to do not change the port ,so I can specity to witch port it to listen , or I have to recompile winedbg ? Thank you!
Judging by the wine source code at file gdbproxy.c (function gdb_startup) [1] it is not possible, the port is always chosen by the OS. It could be changed to support port selection, but I'm curious about why you have such need.
[1] http://source.winehq.org/source/programs/winedbg/gdbproxy.c
Best wishes, Bruno
On Fri, Oct 21, 2016 at 3:15 PM, Bruno Jesus 00cpxxx@gmail.com wrote:
On Wed, Oct 19, 2016 at 1:07 PM, A B dianaxxyyzz@gmail.com wrote:
If i run : winedbg --gdb --no-start test.exe
it say : target remote localhost:55304
But if I run it second time , it say a different port , for example target remote localhost:111111
is there a command line argument for winedbg so it to listen to same port every time , and to do not change the port ,so I can specity to witch port it to listen , or I have to recompile winedbg ? Thank you!
Judging by the wine source code at file gdbproxy.c (function gdb_startup) [1] it is not possible, the port is always chosen by the OS. It could be changed to support port selection, but I'm curious about why you have such need.
[1] http://source.winehq.org/source/programs/winedbg/gdbproxy.c
Actually there is bug https://bugs.winehq.org/show_bug.cgi?id=21404