2 May
2018
2 May
'18
3:01 p.m.
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.