Re: [Qemu-devel] [PATCHv3] report that QEMU process was killed by a signal

2011-03-31 Thread Gleb Natapov
On Wed, Mar 30, 2011 at 09:51:29PM +0100, Peter Maydell wrote: > 2011/3/30 Gleb Natapov : > > On Wed, Mar 30, 2011 at 07:53:41PM +0100, Peter Maydell wrote: > >> I'm not convinced about the utility of printing the pid, personally. > >> Most programs get along fine without printing anything when > >

Re: [Qemu-devel] [PATCHv3] report that QEMU process was killed by a signal

2011-03-30 Thread Gleb Natapov
On Thu, Mar 31, 2011 at 01:35:31AM +0400, malc wrote: > On Wed, 30 Mar 2011, Peter Maydell wrote: > > > On 15 March 2011 11:56, Gleb Natapov wrote: > > > Currently when rogue script kills QEMU process (using TERM/INT/HUP > > > signal) it looks indistinguishable from system shutdown. Lets report >

Re: [Qemu-devel] [PATCHv3] report that QEMU process was killed by a signal

2011-03-30 Thread malc
On Wed, 30 Mar 2011, Peter Maydell wrote: > On 15 March 2011 11:56, Gleb Natapov wrote: > > Currently when rogue script kills QEMU process (using TERM/INT/HUP > > signal) it looks indistinguishable from system shutdown. Lets report > > that QEMU was killed and leave some clues about the killer id

Re: [Qemu-devel] [PATCHv3] report that QEMU process was killed by a signal

2011-03-30 Thread Peter Maydell
2011/3/30 Gleb Natapov : > On Wed, Mar 30, 2011 at 07:53:41PM +0100, Peter Maydell wrote: >> I'm not convinced about the utility of printing the pid, personally. >> Most programs get along fine without printing anything when >> they receive a terminal signal. > Well qemu is a bit of special case.

Re: [Qemu-devel] [PATCHv3] report that QEMU process was killed by a signal

2011-03-30 Thread Gleb Natapov
On Wed, Mar 30, 2011 at 07:53:41PM +0100, Peter Maydell wrote: > On 30 March 2011 19:43, Gleb Natapov wrote: > > On Wed, Mar 30, 2011 at 07:39:31PM +0100, Peter Maydell wrote: > >> Unfortunately this patch causes qemu to segfault when killed > >> via ^C (at least on my Ubuntu maverick system). Thi

Re: [Qemu-devel] [PATCHv3] report that QEMU process was killed by a signal

2011-03-30 Thread Peter Maydell
On 30 March 2011 19:43, Gleb Natapov wrote: > On Wed, Mar 30, 2011 at 07:39:31PM +0100, Peter Maydell wrote: >> Unfortunately this patch causes qemu to segfault when killed >> via ^C (at least on my Ubuntu maverick system). This is because >> it registers a signal handler with sigaction, but then

Re: [Qemu-devel] [PATCHv3] report that QEMU process was killed by a signal

2011-03-30 Thread Gleb Natapov
On Wed, Mar 30, 2011 at 01:49:10PM -0500, Anthony Liguori wrote: > On 03/30/2011 01:39 PM, Peter Maydell wrote: > >On 15 March 2011 11:56, Gleb Natapov wrote: > >>Currently when rogue script kills QEMU process (using TERM/INT/HUP > >>signal) it looks indistinguishable from system shutdown. Lets re

Re: [Qemu-devel] [PATCHv3] report that QEMU process was killed by a signal

2011-03-30 Thread Anthony Liguori
On 03/30/2011 01:39 PM, Peter Maydell wrote: On 15 March 2011 11:56, Gleb Natapov wrote: Currently when rogue script kills QEMU process (using TERM/INT/HUP signal) it looks indistinguishable from system shutdown. Lets report that QEMU was killed and leave some clues about the killer identity.

Re: [Qemu-devel] [PATCHv3] report that QEMU process was killed by a signal

2011-03-30 Thread Gleb Natapov
On Wed, Mar 30, 2011 at 07:39:31PM +0100, Peter Maydell wrote: > On 15 March 2011 11:56, Gleb Natapov wrote: > > Currently when rogue script kills QEMU process (using TERM/INT/HUP > > signal) it looks indistinguishable from system shutdown. Lets report > > that QEMU was killed and leave some clues

Re: [Qemu-devel] [PATCHv3] report that QEMU process was killed by a signal

2011-03-30 Thread Peter Maydell
On 15 March 2011 11:56, Gleb Natapov wrote: > Currently when rogue script kills QEMU process (using TERM/INT/HUP > signal) it looks indistinguishable from system shutdown. Lets report > that QEMU was killed and leave some clues about the killer identity. Unfortunately this patch causes qemu to se

Re: [Qemu-devel] [PATCHv3] report that QEMU process was killed by a signal

2011-03-26 Thread Blue Swirl
On Sat, Mar 26, 2011 at 3:55 PM, Gleb Natapov wrote: > On Sat, Mar 26, 2011 at 03:50:46PM +0200, Blue Swirl wrote: >> On Fri, Mar 25, 2011 at 2:04 PM, Gleb Natapov wrote: >> > Ping? >> >> Does not work: >> INT: >> Got signal 951049944 from pid 0 >> TERM: >> Got signal -1553068904 from pid 0 > You

Re: [Qemu-devel] [PATCHv3] report that QEMU process was killed by a signal

2011-03-26 Thread Gleb Natapov
On Sat, Mar 26, 2011 at 03:50:46PM +0200, Blue Swirl wrote: > On Fri, Mar 25, 2011 at 2:04 PM, Gleb Natapov wrote: > > Ping? > > Does not work: > INT: > Got signal 951049944 from pid 0 > TERM: > Got signal -1553068904 from pid 0 You use SDL correct? This is SDL problem and I fixed it in SDL upstr

Re: [Qemu-devel] [PATCHv3] report that QEMU process was killed by a signal

2011-03-26 Thread Blue Swirl
On Fri, Mar 25, 2011 at 2:04 PM, Gleb Natapov wrote: > Ping? Does not work: INT: Got signal 951049944 from pid 0 TERM: Got signal -1553068904 from pid 0 HUP: Got signal 1 from pid 16185 Even here the pid is not correct, it should be 3098.

Re: [Qemu-devel] [PATCHv3] report that QEMU process was killed by a signal

2011-03-25 Thread Gleb Natapov
Ping? On Tue, Mar 15, 2011 at 01:56:04PM +0200, Gleb Natapov wrote: > Currently when rogue script kills QEMU process (using TERM/INT/HUP > signal) it looks indistinguishable from system shutdown. Lets report > that QEMU was killed and leave some clues about the killer identity. > > Signed-off-b

[Qemu-devel] [PATCHv3] report that QEMU process was killed by a signal

2011-03-15 Thread Gleb Natapov
Currently when rogue script kills QEMU process (using TERM/INT/HUP signal) it looks indistinguishable from system shutdown. Lets report that QEMU was killed and leave some clues about the killer identity. Signed-off-by: Gleb Natapov --- v1->v2: - print message from a main loop instead of