[Bug 44936] New: winedbg + gdb (remote) interaction broken due to recent commits
https://bugs.winehq.org/show_bug.cgi?id=44936 Bug ID: 44936 Summary: winedbg + gdb (remote) interaction broken due to recent commits Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winedbg Assignee: wine-bugs(a)winehq.org Reporter: julius.schwartzenberg(a)gmail.com Distribution: --- I'm using OpenSUSE 42.3. I start winedbg as follows: winedbg --gdb --no-start path/to/smth.exe Then I use Eclipse to connect to the remote port that is shown. This results in: - ../../gdb/infrun.c:5585: internal-error: int finish_step_over(execution_control_state*): Assertion `ecs->event_thread->control.trap_expected' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. - Text I enter in the Debugger Console (in Eclipse) is invisible - Things crash When I revert back to 77d65c39486ffc2b4c17aec958e361b180a029a1 these problems disappear. Please let me know if I should do more analysis. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44936 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12(a)gmail.com -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44936 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|unspecified |3.0 Keywords| |download, regression Regression SHA1| |d1e9694edabe6ef803f1b98de28 | |8982e5d03ab29 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44936 --- Comment #1 from Zebediah Figura <z.figura12(a)gmail.com> --- Created attachment 61212 --> https://bugs.winehq.org/attachment.cgi?id=61212 gdbproxy debug Thanks for the bug report; sorry it took so long to get to. I'm having trouble setting up Eclipse on my own machine, so I'm going to try to ask for debug output and see if that gets me anywhere. Does this happen immediately, or only after setting a breakpoint? If the latter, can you try executing
set debug target 2 set debug infrun 2 set debug remote 2
and attach stderr from the server process (I hope)? If the former it'll be necessary to patch winedbg to execute these on startup; I've attached a patch that should do this if you're willing and able. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44936 --- Comment #2 from Zebediah Figura <z.figura12(a)gmail.com> --- Created attachment 61224 --> https://bugs.winehq.org/attachment.cgi?id=61224 winedbg: Use gdb's default handling of breakpoints. While you're at it, could you also see if this patch makes the bug go away? Thanks. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44936 --- Comment #3 from Julius Schwartzenberg <julius.schwartzenberg(a)gmail.com> --- Also my apologies, I had not been able to look into this more recently. I just tried this with Git revision 9fecb7499531ddbcde7970b4d98df92dbc1bc010 (currently origin/HEAD) without any patches and I cannot reproduce the issues anymore. I now run into another problem however, the program I'm running just quits after I start it in the debugger. (It doesn't when ran without.) I suspect this is unrelated however. Would it help you in general if I'd help you set up Eclipse? For this to work, you need to manually run 'winedbg --gdb --no-start' and use the printed port in Debug Configurations, add a Remote Application and on the Debugger tab->Connection tab fill in the port. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44936 --- Comment #4 from Zebediah Figura <z.figura12(a)gmail.com> --- It was a problem with the package I was using (it kept crashing). I downloaded a more recent version directly from eclipse.org, and I can't seem to reproduce either problem. Following your instructions I seem to be able to attach to a simple test program, enter commands in the debug console, break and correctly step over breakpoints, and get output from the program. Perhaps it's something specific to the program in question? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44936 --- Comment #5 from Julius Schwartzenberg <julius.schwartzenberg(a)gmail.com> --- Possibly. I'm trying to debug ABBYY Lingvo 12 http://web.archive.org/web/*/http://fr7.abbyy.com/lingvo12/ABBYY_Lingvo_12.e... When I do not set any breakpoints I can see it the main window and then it suddenly exits (exited cleanly is printed). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44936 --- Comment #6 from Zebediah Figura <z.figura12(a)gmail.com> --- (In reply to Julius Schwartzenberg from comment #5)
Possibly. I'm trying to debug ABBYY Lingvo 12 http://web.archive.org/web/*/http://fr7.abbyy.com/lingvo12/ABBYY_Lingvo_12. exe
When I do not set any breakpoints I can see it the main window and then it suddenly exits (exited cleanly is printed).
I still can't seem to reproduce this, either with the installer or the program itself. It throws a lot of SIGABRTs, but otherwise the debugger works as well as if I'd started it from the terminal. Do these problems show up for you if you just run 'wine winedbg --gdb foo.exe'? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44936 --- Comment #7 from Julius Schwartzenberg <julius.schwartzenberg(a)gmail.com> --- Yes, I have the same issue then. I use these commands to let execution continue: handle SIGABRT pass nostop noprint handle SIGSEGV pass nostop noprint Maybe that's not the right way? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44936 --- Comment #8 from Zebediah Figura <z.figura12(a)gmail.com> --- (In reply to Julius Schwartzenberg from comment #7)
Yes, I have the same issue then. I use these commands to let execution continue: handle SIGABRT pass nostop noprint handle SIGSEGV pass nostop noprint
Maybe that's not the right way?
I believe that's the right way, yes. I would guess that the program intends to catch these signals. This is with Eclipse, right? It sounds like the debugger is working correctly then; can you help clarify what's failing? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44936 --- Comment #9 from Julius Schwartzenberg <julius.schwartzenberg(a)gmail.com> --- No I ran 'wine winedbg --gdb foo.exe' from the command line (no Eclipse involved), used these when I got a prompt for the first SIGABRT: handle SIGABRT pass nostop noprint handle SIGSEGV pass nostop noprint Then did 'cont' to continue. Then I see the program pop up and then it just closes by itself. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44936 --- Comment #10 from Zebediah Figura <z.figura12(a)gmail.com> --- (In reply to Julius Schwartzenberg from comment #9)
No I ran 'wine winedbg --gdb foo.exe' from the command line (no Eclipse involved), used these when I got a prompt for the first SIGABRT: handle SIGABRT pass nostop noprint handle SIGSEGV pass nostop noprint
Then did 'cont' to continue. Then I see the program pop up and then it just closes by itself.
Okay, thanks for bearing with me. When I do this (with Lingvo.exe), the program shows a window saying "The trial period has expired for the following", and prompting me to activate or exit. There are signs of bug 45070 when I close the program: wine client error:8e: write: Bad file descriptor but otherwise it works as I'd expect. Is it something that only shows up after you activate? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44936 --- Comment #11 from Julius Schwartzenberg <julius.schwartzenberg(a)gmail.com> --- Hmm, it never offered you a trial period? I indeed have a patched version which does not show this. Maybe that could indeed be the problem, I will try an unpatched version. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44936 --- Comment #12 from Zebediah Figura <z.figura12(a)gmail.com> --- It might be worth retesting this, if the circumstances under which it occurred can still be reproduced. A lot has changed in the gdb proxy, mostly around wine 5.6 or so. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44936 Jinoh Kang <jinoh.kang.kr(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jinoh.kang.kr(a)gmail.com --- Comment #13 from Jinoh Kang <jinoh.kang.kr(a)gmail.com> --- Can reproduce in wine 7.12 (staging) while debugging foobar2000.exe. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44936 Alex Henrie <alexhenrie24(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alexhenrie24(a)gmail.com Summary|winedbg + gdb (remote) |winedbg + gdb (remote) |interaction broken due to |interaction broken since |recent commits |Wine 3.1 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44936 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |source -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44936 --- Comment #14 from Zeb Figura <z.figura12(a)gmail.com> --- (In reply to Jinoh Kang from comment #13)
Can reproduce in wine 7.12 (staging) while debugging foobar2000.exe.
If this is still reproducible, can you please provide reproduction steps? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44936 --- Comment #15 from Jinoh Kang <jinoh.kang.kr(a)gmail.com> --- (In reply to Zeb Figura from comment #14)
(In reply to Jinoh Kang from comment #13)
Can reproduce in wine 7.12 (staging) while debugging foobar2000.exe.
If this is still reproducible, can you please provide reproduction steps?
I don't recall exact reproduction steps. IIRC it has only happened ever once, and never appeared again. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla