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

Segfault with multiple debuggers open #662

Closed
AntyMew opened this issue Apr 14, 2017 · 1 comment
Closed

Segfault with multiple debuggers open #662

AntyMew opened this issue Apr 14, 2017 · 1 comment
Labels
port:Qt Affects the Qt version (the standard desktop version) severity:host crash Issues that cause the emulator itself to crash
Milestone

Comments

@AntyMew
Copy link
Contributor

AntyMew commented Apr 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:

  • Open CLI debugger
  • Break
  • Start GDB server
  • Send any command to CLI debugger

This does not affect the SDL port, as it will not open if both -d and -g are passed.

@endrift endrift added this to the 0.6.0 milestone Apr 14, 2017
@endrift
Copy link
Member

endrift commented Apr 14, 2017

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 endrift added the port:Qt Affects the Qt version (the standard desktop version) label Apr 14, 2017
@endrift endrift added the severity:host crash Issues that cause the emulator itself to crash label Apr 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
port:Qt Affects the Qt version (the standard desktop version) severity:host crash Issues that cause the emulator itself to crash
Projects
None yet
Development

No branches or pull requests

2 participants