Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

gdb: cannot debug windows/386 binaries in wine/gdb due to internal gdb assert failure #7629

Open
andlabs opened this issue Mar 25, 2014 · 3 comments
Open

gdb: cannot debug windows/386 binaries in wine/gdb due to internal gdb assert failure #7629

andlabs opened this issue Mar 25, 2014 · 3 comments
Labels
OS-Windows
Milestone
Unplanned

Comments

@andlabs
Copy link
Contributor

andlabs commented Mar 25, 2014 

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.
@andlabs
Copy link
Contributor Author

andlabs commented Mar 25, 2014

Comment 1:

...I'm a dunce and didn't proofread that.
CORRECT INSTRUCTIONS
1. Build a Go program — any Go program — for windows/386.
2. winedbg --gdb program.exe
3. Alternatively, winedbg --gdb --no-start program.exe, then attach the resultant gdb
server to a debugging frontend; same effect.

@gopherbot
Copy link

Comment 2 by chandran.gnana:

T

@ianlancetaylor
Copy link
Contributor

Comment 3:

Labels changed: added repo-main, release-none, os-windows.

@bradfitz bradfitz removed the new label Dec 18, 2014
@rsc rsc removed the os-windows label Apr 10, 2015
@rsc rsc added this to the Unplanned milestone Apr 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
OS-Windows
Projects
None yet
Milestone
Unplanned
Development

No branches or pull requests
5 participants
@bradfitz @rsc @andlabs @ianlancetaylor @gopherbot