If the target is waiting for any input (eg. scanf), sgdb isn't currently handling this, and the way program execution currently works is that sgdb is waiting for any response indefinitely, which eventually hangs up the GUI since this is done inside an event handler. There should be two jobs in parallel, one reading the response and the other one checking for any input, which terminates the response read job (somehow, you're not supposed to terminate a thread so ig I have to find out another way).
If the target is waiting for any input (eg. scanf), sgdb isn't currently handling this, and the way program execution currently works is that sgdb is waiting for any response indefinitely, which eventually hangs up the GUI since this is done inside an event handler. There should be two jobs in parallel, one reading the response and the other one checking for any input, which terminates the response read job (somehow, you're not supposed to terminate a thread so ig I have to find out another way).