https://bugs.winehq.org/show_bug.cgi?id=51765 --- Comment #1 from Konstantin Kharlamov <hi-angel(a)yandex.ru> --- When running with `WINEDBG=+all`, these are the lines when error happens: 3118.471:0020:0024:Call winex11.drv.GetDC(1001004f,0002002c,0002002c,0032f790,0032f7a0,00000013) ret=6ed71d74 3118.471:0020:0024:err:x11drv:error_handler X protocol error: serial=766, request_code=149 - breaking into debugger 3118.471:0020:0024:Call ntdll.DbgBreakPoint() ret=7d770c7a 3118.471:0020:0024:trace:seh:dispatch_exception code=80000003 flags=0 addr=7BC504C0 ip=7bc504c0 tid=0024 3118.471:0020:0024:trace:seh:dispatch_exception info[0]=00000000 3118.471:0020:0024:warn:seh:dispatch_exception EXCEPTION_BREAKPOINT exception (code=80000003) raised Any ideas, how to make winedbg actually stop execution when error happens? The line ntdll.DbgBreakPoint() says that debugger should have stopped when error happened — but this is not what happens. When running under winegdb, it ends with `Process of pid=0114 has terminated`. Is there perhaps a trick to make winedbg work? -- 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.