Re: [MiNT] patch:MiNT:single-task

[Alan Hourihane <alanh@fairlite.co.uk>]

Helmut,

It sounds like this is more useful in the DEBUG FreeMiNT kernel.

I think I'd be happy wrapping this up with that as it seems that the
Pure-Debugger is a pretty low level application and using that with a
FreeMiNT kernel with DEBUG capabilities sounds like a match.

How about wrapping your patch hunks with...

#ifdef SINGLE_TASK
...
#endif

and then in KERNELDEFS you can add SINGLE_TASK as a new build option.

You could commit your code as is then but it would be easy to disable if
there are problems.

Thanks,

Alan.

On Wed, 2010-06-02 at 16:38 +0000, Helmut Karlowski wrote:
> 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
> 
>