[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#971054: marked as done (winedbg --gdb does not work with 32-bit WINEPREFIX)

Your message dated Mon, 6 Jun 2022 03:10:21 +0000
with message-id <CANTw=MM+ftSgeR82MzK2y7YT_bmtAGgSZcTBM=yauZi2+8GKqg@mail.gmail.com>
and subject line Re: Bug#971054: winedbg --gdb does not work with 32-bit WINEPREFIX
has caused the Debian Bug report #971054,
regarding winedbg --gdb does not work with 32-bit WINEPREFIX
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 owner@bugs.debian.org
immediately.)


-- 
971054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971054
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wine
Version: 5.0-4
Severity: normal

Hi,

Trying to use the --gdb flag with winedbg does not work with 32-bit
WINEPREFIXes. Instead of spawning gdb, it just exits:

user@host:~$ WINEPREFIX=~/.wine32 winedbg --gdb notepad.exe
002a:002b: create process 'C:\windows\system32\notepad.exe' /0x1106b0 @0x7fa07e50 (0<0>)
002a:002b: create thread I @0x7fa07e50
user@host:~$

Running the same command with a 64-bit prefix works as expected:

user@host:~$ winedbg --gdb notepad.exe
002b:002c: create process 'C:\windows\system32\notepad.exe'/0x10980 @0x7f8993d81b60 (0<0>)
002b:002c: create thread I @0x7f8993d81b60
GNU gdb (Debian 8.2.1-2+b3) 8.2.1

<snip>

002b:002c: loads DLL C:\windows\system32\uxtheme.dll @0x7f8990940000 (0<0>)
warning: remote target does not support file transfer, attempting to access files from local filesystem.
0x000000007bc961e5 in DbgBreakPoint () from /usr/lib/wine/../x86_64-linux-gnu/wine/ntdll.dll.so
Wine-gdb>



I was able to reproduce the issue on a VM running only bullseye i386 (no
foreign architectures), so it doesn't appear to be a multi-arch related issue.

Also, the upstream packages work as expected on bullseye i386. I
haven't tested them on buster.


Tested, not working:
-------------------

Buster, amd64, wine 4.0-2 from buster repo, 32-bit WINEPREFIX
Bullseye, i386, wine 5.0-4 from bullseye repo, 32-bit WINEPREFIX


Tested, working as expected:
---------------------------

Buster, amd64, wine 4.0-2 from buster repo, 64-bit WINEPREFIX
Bullseye, i386, winehq-stable 4.0.2~bullseye from winehq repo, 32-bit WINEPREFIX
Bullseye, i386, winehq-stable 5.0.2~bullseye from winehq repo, 32-bit WINEPREFIX
Bullseye, i386, winehq-devel 5.18~bullseye from winehq repo, 32-bit WINEPREFIX


Best regards,
Bill

--- End Message ---
--- Begin Message --- 
version: 6.0+repack-1

On Sat, Sep 26, 2020 at 9:00 PM William Blough wrote:
> Trying to use the --gdb flag with winedbg does not work with 32-bit
> WINEPREFIXes. Instead of spawning gdb, it just exits:

--- End Message ---
Reply to: