On Wed, 13 Mar 2013 08:51:14 +1100
Lex Trotman ele...@gmail.com wrote:
On 13 March 2013 04:47, Dimitar Zhekov dimitar.zhe...@gmail.com wrote:
When you execute a gdb -exec-interrupt command in debugger or Scope, a
SIGINT is sent to the inferior, and to gdb, and to Geany. But if you
start
On 13 March 2013 04:47, Dimitar Zhekov dimitar.zhe...@gmail.com wrote:
On Mon, 11 Mar 2013 13:18:10 +1100
Lex Trotman ele...@gmail.com wrote:
Geany currently uses SIGQUIT to terminate a running program (using the
execute menu item or toolbar button when it shows the stop icon).
This has
On 11/03/13 05:17, Lex Trotman wrote:
On 11 March 2013 14:58, Chow Loong Jin hyper...@gmail.com wrote:
On 11/03/2013 10:18, Lex Trotman wrote:
Hi All,
[...]
My understanding of Unix/Linux signals is that the comment above is
wrong and always has been wrong, a signal sent to a child process
On 12 March 2013 08:25, Enrico Tröger enrico.troe...@uvena.de wrote:
Hey Lex,
did you intentionally answered off-list?
Nah, your mail was to list and cc me, so the smart mailer chose to
reply to you, and its too early in the morning for me to notice :)
This cced to the list for the record :)
Le 11/03/2013 23:42, Lex Trotman a écrit :
[...]
But it's probably not that hard to implement on older versions
ourselves, even if it simply means to borrow the relevant code…
As Enrico said, Glad you volunteered :)
Nah, it doesn't work, you aren't Enrico ;)
A final comment is that since
Hi All,
Geany currently uses SIGQUIT to terminate a running program (using the
execute menu item or toolbar button when it shows the stop icon).
This has always been the case since the stop button was added.
There is a big comment in the code explaining why SIGQUIT is used, and
its problems:
On 11/03/2013 10:18, Lex Trotman wrote:
Hi All,
[...]
My understanding of Unix/Linux signals is that the comment above is
wrong and always has been wrong, a signal sent to a child process by a
parent process does not get delivered to the parent.
I don't know if anybodys memory is good
