Your message dated Mon, 08 Feb 2016 13:22:59 +0100
with message-id <c0103ca00e8aa6652d1f81e261122...@sk2.org>
and subject line Re: Bug#814079: [gdb-mingw-w64] Fails to connect to gdbserver
has caused the Debian Bug report #814079,
regarding [gdb-mingw-w64] Fails to connect to gdbserver
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
814079: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814079
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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:5555 path/to/something.exe
and it prints
Process path/to/something.exe created; pid = 41
Listening on port 5555
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:5555
and I get just:
Remote debugging using 127.0.0.1:5555
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 wily ppa.launchpad.net
500 unstable http.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 experimental http.debian.net
--- Package information. ---
Package's Depends field is empty.
Package's Recommends field is empty.
Package's Suggests field is empty.
--
- Jan Hudec <b...@ucw.cz>
--- End Message ---
--- Begin Message ---
Le 08/02/2016 12:17, Jan Hudec a écrit :
On Monday 08 of February 2016 11:22:38 Stephen Kitt wrote:
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 5555 (which would explain your other symptoms).
Hm, yes, I do.
And this is the culprit:
$ netstat -ptn | grep 5555
tcp 0 0 127.0.0.1:47022 127.0.0.1:5555
ESTABLISHED 5510/adb
tcp 0 0 127.0.0.1:5555 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.
You're welcome! It's nice to know there are users of the gdb-mingw-w64
packages ;-).
I am somewhat surprised that it just stopped working sometime last week
though, because I've been using adb quite long.
It is surprising, yes; I don't know what could explain it, unless
something started listening on port 5554, or perhaps you upgraded to adb
6 (that's a stab in the dark, I don't know if its behaviour has
changed).
Regards,
Stephen
--- End Message ---
