Your message dated Sun, 6 Sep 2015 16:21:16 +0200
with message-id <[email protected]>
and subject line Re: Bug#734166: gdb-mingw-w64: cross architecture 32bit/64bit
debugging is not working on i386/x68_64
has caused the Debian Bug report #734166,
regarding gdb-mingw-w64: cross architecture 32bit/64bit debugging is not
working on i386/x68_64
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 [email protected]
immediately.)
--
734166: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734166
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gdb-mingw-w64
Version: 7.6-4+7
Severity: normal
Even though gdb-mingw-64 installs x86_64-mingw32-gdb and i386-w64-mingw64-gdb
either of them is not working (at least on x86_64).
In particular, gdb refuses to connect to the corresponding gdbserver as the
architectures i368 and i386:x68_64 look incompitible to it.
It seems to me that biarch debugging seems not to be working properly for
mingw64 in gdb.
I suggest one of two possible solutions:
• activate biarch debugging for mingw64
• use multiarch to coinstall the packages for i386 and x86_64
The first one is probably more clean, and avoids installing unnecssary
packages.
The secound one does not involve interaction with upstream, but installs
additional packages (e.g. python) for i386 on x68_64. Unfortunately, there are
some multiarch issues with these packages.
-- System Information:
Debian Release: jessie/sid
APT prefers testing-proposed-updates
APT policy: (500, 'testing-proposed-updates'), (500, 'oldstable-updates'),
(500, 'unstable'), (500, 'testing'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
mingw64-windows
mingw64-x86v64
mingw64-amd64
Kernel: Linux 3.12-1-amd64 (SMP w/6 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gdb-mingw-w64 depends on:
ii gdb 7.6.1-1
ii libc6 2.17-97
ii libexpat1 2.1.0-4
ii libncurses5 5.9+20130608-1
ii libpython2.7 2.7.6-4
ii libreadline6 6.2+dfsg-0.1
ii libtinfo5 5.9+20130608-1
ii zlib1g 1:1.2.8.dfsg-1
Versions of packages gdb-mingw-w64 recommends:
ii gdb-mingw-w64-target 7.6-4+7
gdb-mingw-w64 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sat, 4 Jan 2014 17:22:59 +0100, Stephen Kitt <[email protected]> wrote:
> On Sat, 04 Jan 2014 14:54:59 +0100, Tobias Schlemmer
> <[email protected]> wrote:
> > Even though gdb-mingw-64 installs x86_64-mingw32-gdb and
> > i386-w64-mingw64-gdb either of them is not working (at least on x86_64).
> >
> > In particular, gdb refuses to connect to the corresponding gdbserver as
> > the architectures i368 and i386:x68_64 look incompitible to it.
>
> Could you explain exactly what you're trying to do?
>
> Here's how I use gdbserver:
> * on the Windows host
> gdbserver localhost:2345 c:\windows\system32\notepad.exe
> * on the Linux host
> i686-w64-mingw32-gdb
> (gdb) target remote 192.168.1.6:2345
> (gdb) cont
> and Notepad starts properly.
>
> (Obviously for real I'd start the executable I'm interested in and point
> Linux gdb at it as well.)
>
> My 64-bit Windows machine isn't here so I can't check that just now, but it
> worked the last time I used it.
Given the lack of response, and the fact that I can't reproduce this bug, I'm
closing it.
Regards,
Stephen
pgp0nlZcKcq0x.pgp
Description: OpenPGP digital signature
--- End Message ---
