[Github-comments] [geany/geany] Handle continuous G_IO_IN-s without any data (#1461)

[J-Dunn]

I have applied the patch and built geany and plugins from master in each case. Debugger no longer locks up bit I don't seem to get what I expect from the debugger. This may be my not knowing how to use it since it has never worked since I tried to install it. 
```

int main () {
  #include <stdio.h>
  printf ("%s","hello worlds.\n\r");
  return (0);
}
```

I have build this with build command configured as follows:

gcc -g3 -Wall -c "%f"

the compiler window shows:
```
gcc -g3 -Wall -c "main" "main.c" (in directory: <local path to source>)
Compilation finished successfully.

```
When I simply run it with the gear wheel icon, I get a vte terminal with the output msg. Fine.

When I set break point in the return in line 4 and try to run it with Debug|Run/Continue the status bar appears show "Busy" but I do not see anything in Stack, Memory or Program Terminal tabs.

None of the debug functions like step are enabled, only 'terminate' is possible.

At This point I was expecting to be able to step the prog in the debugger and to already see the 'hello worlds' in a terminal somewhere. Also I was expecting some indication in the editor that execution was halted on line 4 or main.c  ; this does not seem to be the state of play.

As far as I can tell from limited help description, this should be what is happening at this stage. 

Am I missing something or are there still problems with debugging after the spawn lockup is fixed?



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/1461#issuecomment-355553238
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.geany.org/pipermail/github-comments/attachments/20180105/fce92485/attachment.html>