Bug#814079: [gdb-mingw-w64] Fails to connect to gdbserver

[Stephen Kitt]

Hi Jan,

Le 08/02/2016 10:07, Jan Hudec a écrit :

On one terminal I start the program to debug under wine and gdbserver:

$ wine /usr/share/win32/gdbserver.exe localhost: 
path/to/something.exe


and it prints

Process path/to/something.exe created; pid = 41
Listening on port 
Remote debugging from host 127.0.0.1


Do you get the third line immediately? It's only printed when a remote 
debugger connects, so you shouldn't get it then unless something else is 
connecting to port  (which would explain your other symptoms).


[...]

Regards,

Stephen

Bug#814079: [gdb-mingw-w64] Fails to connect to gdbserver

[Jan Hudec]

On Monday 08 of February 2016 11:22:38 Stephen Kitt wrote:
> Hi Jan,
> 
> Le 08/02/2016 10:07, Jan Hudec a écrit :
> > On one terminal I start the program to debug under wine and gdbserver:
> > $ wine /usr/share/win32/gdbserver.exe localhost:
> > 
> > path/to/something.exe
> > 
> > and it prints
> > 
> > Process path/to/something.exe created; pid = 41
> > Listening on port 
> > Remote debugging from host 127.0.0.1
> 
> Do you get the third line immediately? It's only printed when a remote
> debugger connects, so you shouldn't get it then unless something else is
> connecting to port  (which would explain your other symptoms).

Hm, yes, I do.

And this is the culprit:
$ netstat -ptn | grep 
tcp0  0 127.0.0.1:47022 127.0.0.1:  
ESTABLISHED 5510/adb
tcp0  0 127.0.0.1:  127.0.0.1:47022 
ESTABLISHED 17476/gdbserver.exe 

So I need to retrain my muscle memory to use different port (yes, it turned 
out to work). Thank you for help.

I am somewhat surprised that it just stopped working sometime last week 
though, because I've been using adb quite long.

-- 
 - Jan Hudec 

Bug#814079: [gdb-mingw-w64] Fails to connect to gdbserver

[Jan Hudec]

Package: gdb-mingw-w64
Version: 7.10-1+10.2
Severity: grave

--- Please enter the report below this line. ---

On one terminal I start the program to debug under wine and gdbserver:

$ wine /usr/share/win32/gdbserver.exe localhost: path/to/something.exe

and it prints

Process path/to/something.exe created; pid = 41
Listening on port 
Remote debugging from host 127.0.0.1

and waits for the connection. Ok so far. On another terminal, I start gdb and 
try to connect:

$ i686-w64-mingw32-gdb path/to/something.exe
(gdb) target remote localhost:

and I get just:

Remote debugging using 127.0.0.1:
Ignoring packet error, continuing...
warning: unrecognized item "timeout" in "qSupported" response
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Bogus trace status reply from target: timeout

The terminal with wine does not show anything new.

Very, very rarely it manages to connect, but most of the time it just shows 
this. It used to work.

I have both gdb-mingw-w64 and gdb-mingw-w64-target version 7.10-1+10.2 and 
wine 1.8-6.

--- System information. ---
Architecture: amd64
Kernel:   Linux 4.3.0-1-amd64

Debian Release: stretch/sid
  990 testing http.debian.net 
  500 wilyppa.launchpad.net 
  500 unstablehttp.debian.net 
  500 trusty  ppa.launchpad.net 
  500 testing-proposed-updates http.debian.net 
  500 stable-updates  ftp.cz.debian.org 
  500 stable  security.debian.org 
  500 stable  ftp.cz.debian.org 
1 experimentalhttp.debian.net 

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.



-- 
 - Jan Hudec