-
Notifications
You must be signed in to change notification settings - Fork 507
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
underlying gdb process has been killed after running to first breakpoint #218
Comments
I should also mention that I can debug this and other programs just fine using gdb on the command line. |
Thanks for filing. It might be a gdb bug in its machine interface implementation. Unfortunately with the info you provided I don't know what the cause is. Maybe if you re-run with |
I'm not sure what you mean. Is "strace" a specific gdb or gdbgui command? I'm running on Windows 10, isn't strace a linux utility? |
Yes strace intercepts and prints all system calls. You're right that it might not be available on windows (I am pretty Linux centric). It might be available as a package in mingw. Or there might be another utility available to debug the issue. What I'm really looking for is a way to see what is causing the abrupt exit, which is likely due to a segfault. The info you provided is not quite specific enough to be actionable since I can't tell what the root cause is (lots of things can cause a segfault). |
I am running into this issue, too. The differenences in my information are this: I do have strace on Windows, and this is the relevant part of my strace log: Exception 0xc0000005 is the exception code for a Memory Access Violation a.k.a Segfault. I can provide the full log if necessary. Update: |
Is there a diagnostic code that gdbgui can output when it catches a segv from GDB? I'm seeing the same error code when starting an app via GDB. |
gcc版本出现问题,找一个适合的mingw,下面是我用的版本,测试能够使用 |
Describe the bug
I load my binary, manually set a break-point several statements into my main function, then click run. The program spawns multiple threads as expected (it's using SDL2) but once it reaches the first break-point, execution stops, the gui is updated, and I see the following in red text in the gdbgui console:
Screenshots

Please complete the following information:
gdbgui -v
): 0.12.0.0gdb -v
): 8.1pip freeze
):cffi==1.11.5
click==6.7
Flask==0.12.4
Flask-Compress==1.4.0
Flask-SocketIO==2.9.6
gdbgui==0.12.0.0
gevent==1.3.4
greenlet==0.4.13
itsdangerous==0.24
Jinja2==2.10
MarkupSafe==1.0
pycparser==2.18
pygdbmi==0.8.3.0
Pygments==2.2.0
python-engineio==2.2.0
python-socketio==2.0.0
six==1.11.0
Werkzeug==0.14.1
Additional context
If it helps, I'm using the neuwin.net Mingw distro. Pretty light as far as mingw on windows gets.
The text was updated successfully, but these errors were encountered: