[Bug 44018] New: winedbg: Can't interrupt program with Ctrl-C

https://bugs.winehq.org/show_bug.cgi?id=44018

Bug ID: 44018
           Summary: winedbg: Can't interrupt program with Ctrl-C
           Product: Wine
           Version: 2.21
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: winedbg
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Created attachment 59682
  --> https://bugs.winehq.org/attachment.cgi?id=59682
log

Hi,

Came across this win64 program that winedbg has trouble with:
Sending a bunch of Ctrl-C displays:

^CCtrl-C: stopping debuggee
  ^CCtrl-C: stopping debuggee
  ^CCtrl-C: stopping debuggee

But we never get back to winedbg's prompt so there's no way to type commands.
Any help with this very much appreciated.

Set of files to replicate the issue can be downloaded from:
  http://tinyurl.com/y6vh9yqd

Tested on Ubuntu 16.04 x86_64,
Tried both stable (2.0.3) and devel (2.0.21) wine packages from
  https://dl.winehq.org/wine-builds/ubuntu

Also tried running it in wineconsole or attaching process in winedbg
from another shell, didn't help.

Log: see attachment

[Bug 44018] winedbg: Can't interrupt program with Ctrl-C

https://bugs.winehq.org/show_bug.cgi?id=44018

Mihai Todor  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #1 from Mihai Todor  ---
Can you please try running `wine64 winedbg Hira.exe` and let me know if that
works? Unfortunately, the debug experience is not so great on x64 apps because
it can't interpret the symbols AFAIK.

[Bug 44018] winedbg: Can't interrupt program with Ctrl-C

https://bugs.winehq.org/show_bug.cgi?id=44018

--- Comment #2 from [e-mail] ---
'wine64 winedbg Hira.exe' works,
We get winedbg's prompt at the beginning and also on Ctrl-C, awesome.

Maybe winedbg could be made to complain (or do the right thing) when it's not
run like this for win64 apps ? This can be confusing from a user perspective.
Or maybe i missed it in the docs

Looks like win32 symbols are showing up in the stack traces, but i guess no x64
symbols for now. Any workarounds ? Otherwise no big deal, this is quite
workable already.

Thanks

[Bug 44018] winedbg: Can't interrupt program with Ctrl-C

https://bugs.winehq.org/show_bug.cgi?id=44018

--- Comment #3 from Mihai Todor  ---
I got bitten by this issue twice (I managed to forget how I made it work the
first time), so I'm glad I was able to help :)

I'd also like to have winedbg autodetect the build type, but not sure if there
is anyone working on this. Same for the symbols.