Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
gdb: cannot debug windows/386 binaries in wine/gdb due to internal gdb assert failure #7629
What does 'go version' print? go version devel +26aa53304a48 Fri Mar 07 16:08:12 2014 -0500 linux/amd64 What steps reproduce the problem? If possible, include a link to a program on play.golang.org. 1. Build a Go program emdash any Go program emdash for windows/386. 2. wine --gdb program.exe 3. Alternatively, wine --gdb --no-start program.exe, then attach the resultant gdb server to a debugging frontend; same effect. What happened? xe: gdbproxy.c:2494: gdb_init_context: Assertion `gdbctx->process == ((void *)0) && de.dwProcessId == dbg_curr_pid' failed. winedbg: Internal crash at 0xf7746430 /tmp/winegdb.2uyltD:2: Error in sourced command file: Remote communication error. Target disconnected.: Connection reset by peer. If attaching to a frontend, the "Connection reset" line will appear in the frontend and the others in the terminal where winedbg is being run. What should have happened instead? (standard gdb prompt and session) Please provide any additional information below. Not sure if this affects windows/amd64 as well; that has its own problems working in wine/winedbg.