Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upSegfault with multiple debuggers open #662
Comments
endrift
added this to the 0.6.0 milestone
Apr 14, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
endrift
Apr 14, 2017
Member
hhhh I thought I fixed this. It's supposed to detach the CLI debugger if you start the GDB server.
Anyway this is one of the reasons I haven't released 0.6 yet--the CLI debugger UI isn't well tested yet.
endrift
commented
Apr 14, 2017
•
edited
Edited 1 time
-
endrift
edited Apr 14, 2017 (most recent)
edited
Edited 1 time
-
Apr 14, 2017 (most recent)
|
hhhh I thought I fixed this. It's supposed to detach the CLI debugger if you start the GDB server. Anyway this is one of the reasons I haven't released 0.6 yet--the CLI debugger UI isn't well tested yet. |
endrift
added
the
port:Qt
label
Apr 14, 2017
endrift
added
the
severity:host crash
label
Apr 15, 2017
endrift
closed this
in
01832ec
Apr 21, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
AntyMew commentedApr 14, 2017
Build: 0.6-4426-d16df697 and 0.1-medusa-4856-8fcf9bee
OS: Debian 9.0 stretch amd64
With both GDB stub and CLI debugger active, sending a command to the CLI debugger segfaults.
Easiest way to reproduce:
This does not affect the SDL port, as it will not open if both
-dand-gare passed.