From mint-bounce@lists.fishpool.fi  Wed Jun  2 12:38:51 2010
Message-ID: <650342.1432312-sendEmail@descaro>
From: "Helmut Karlowski" <helmut.karlowski@ish.de>
To: "Alan Hourihane" <mint@lists.fishpool.fi>
Cc: "helmut.karlowski@ish.de" <helmut.karlowski@ish.de>
Subject: Re: [MiNT] patch:MiNT:single-task
Date: Wed, 2 Jun 2010 16:38:05 +0000
X-Mailer: sendEmail-1.55
MIME-Version: 1.0
Content-Type: multipart/related; boundary="----MIME delimiter for sendEmail-494556.994018243"
X-Antivirus: avast! (VPS 100602-0, 02.06.2010), Outbound message
X-Antivirus-Status: Clean
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-to: mint-bounce@lists.fishpool.fi
X-original-sender: helmut.karlowski@ish.de
Precedence: bulk
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
List-Id: <mint.lists.fishpool.fi>
X-List-ID: <mint.lists.fishpool.fi>
List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
List-owner: <mailto:tjhukkan@fishpool.fi>
List-post: <mailto:mint@lists.fishpool.fi>

This is a multi-part message in MIME format. To properly display this message you need a MIME-Version 1.0 compliant Email program.

------MIME delimiter for sendEmail-494556.994018243
Content-Type: text/plain;
  charset="iso-8859-1"
  Content-Transfer-Encoding: quoted-printable

Alan Hourihane wrote:

> > I meant a test inside MiNT - something like f->links > 0 or whatever. PD
> > does not do anything with -1, but the debugged apps may call a
> > Fclose(-1) before they exit for some reason. And these apps are PD for
> > MiNT so it has no kbd after the PD-client has exited.
>
> I think we need to understand why apps call Fclose(-1) and what they
> expect first.

Something like give the console back to the system? - I don't know.

> > > Are you saying that sending a signal such as SIGKILL to the
> > > application wouldn't stop it ?
> >
> > Where did I say that? You can kill PD for example using the taskmanager
> > (once the PD-client does AES-calls). But this is at own risk ;)
>
> Then I'm misunderstanding what you mean by is not stopped. Can you
> clarify ?

XaAES stops all its clients except the ones that have F_DONT_STOP set.
When you debug a console-app (like MicroEmacs) you need toswin for this.

> > > Are you saying you get no key events when using the current code ?
> >
> > Yes.
>
> O.k. I think we need to understand if PD really is disabling timers
> here.

At least it does something obscure. But non-AES-progs continue
running so maybe its something else. All I know is the first call to
addroottimeout stops the keyboard.

-Helmut



------MIME delimiter for sendEmail-494556.994018243--


