signal catching in PeeWeeLinux

[Dr Jaime V. Miro]

Hi,

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
---------------------------------------------------