One more thing, after pressing the 'X' button several times and JUST BEFORE the last time that causes the crash, the following message appears in the octave console: " panic: Interrupt -- stopping myself...
attempting to save variables to `octave-core'... save to `octave-core' complete " This shows that the crash occurs when you try to kill octave and it's already gone. On Wed, 2008-08-13 at 10:13 +0000, Noam Lewis wrote: > Bug reproduced with strace-ing. > The problem seems to be that it sends a SIGINT to the init process (pid 0): > See the end of the attached strace log: > > 8587 kill(0, SIGINT) > > You can try it yourself by simply running qtoctave and pressing the 'X' > button _several_ times. > I'm not a QT whiz, but maybe you should read this: > http://doc.trolltech.com/3.3/qprocess.html#kill > (Instead of calling the 'kill' system call directly) > > and this: > http://doc.trolltech.com/3.3/qprocess.html#isRunning > > My guess is that QTOctave is trying to kill the connection process after > it has been killed. > > > > ** Attachment added: "qtoctave_strace.log.gz" > http://launchpadlibrarian.net/16739492/qtoctave_strace.log.gz > -- QtOctave "Stop process" button killed Xorg https://bugs.launchpad.net/bugs/251133 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
