signal catching in PeeWeeLinux

[Dr Jaime V. Miro]

Hi Adi,


Adi Linden wrote:
> 
> Hi,
> 
> When you say it works fine on the development system, are you starting it
> from init on your redhat 6.1 system just as you do in PWL?

In PWL the response is the same, whether my code being started from init or from an interactive shell after loggin in. Hence, in the development system in RH6.1 I have not bother testing from init, since it works from a shell.  I believe it should work from the (PWL) shell first (as it does in RH6.1), and then I'll worry about starting from init (from all the mails that I got back as an answer to this problem, I believe I know how to work that out ... once the application works from the (PWL)
shell). One step at a time.


> 
> The majority of changes between 0.51 and 0.53 are relating to the
> pwlconfig scripts. The kernel has been upgraded to 2.2.17 and some minor
> packages were added.


I was focused on getting my stuff working, and I don't think is the kernel, so I haven't updated yet. Also, there were quite a few buggy scripts reports that seem to be sorted now, so I will give it a shot soon.

> 
> Do you have a sample application to 'play' with? Then I can see if I can
> recreate your problem...

Right now the application is kinda biggish (a few threads and shared areas of memo), so I'll try and get a cut down version with the problem. Any pointers welcome meanwhile. 

Thanks

Jaime


> 
> TTYL,
> Adi
> 
> > I've sent a few posting lately regarding signal catching during
> > booting-up (see messages above, in Nov'00), only to realise that the
> > problem I am having is not specific to the boot-up process but seems to
> > be general to PWL.
> >
> > Essentially, I am writing an application that needs catching a signal
> > sent by the user. I dont't need a shell, being an embedded application,
> > so I have chosen SIGQUIT (typing Ctrl+\ in kdb, but it could also easily
> > be SIGINT, by typing CTRL+C). The application has been writen in a RH6.1
> > development machine with kernel 2.2.12, and static libraries linked into
> > it. It works fine.
> >
> > Now, I have PeeWeeLinux 0.51, which casually seems to be based on the
> > same system (RH6.1). I've got it working fine. Boots up, gives me the
> > prompt, loging in. No probs. Now, if I run my application (previosly
> > copied accross from the dev machine), it starts fine, and works fine,
> > but never catches the signal, i.e., loops forever. While this is the
> > behaviour that will exhibit in the future, when it is a proper embedded
> > system, during development is proving a pain to have to shutdown the
> > system (ctrl+alt+del works, hence that signal is being cought by init, I
> > guess) to terminate the application.
> >
> > I can't quite work out the reason. Maybe I should link something else
> > in PWL? maybe upgrading to 0.53 will solve it? (does not seem the reason
> > to me, though)
> >
> > Any wild guesses? Thanks very much in advance,
> >
> > Jaime
> 
> ---------------------------------------------------
> See the list archives at http://adis.on.ca/archives/
> See the PWL homepage at  http://peeweelinux.com
> ---------------------------------------------------

-- 
Dr Jaime V. Miro
Sw and control systems analyst
H2eye Ltd
24-28 Hatton Wall
London EC1N 8JH

Tel:020-7404 9600
Fax:020-7404 9490
j.v.miro@h2eye.com

---------------------------------------------------
See the list archives at http://adis.on.ca/archives/
See the PWL homepage at  http://peeweelinux.com
---------------------------------------------------