My mistake. After further review, uClinux behaves properly (read
like regular old Linux) with socket and files io calls when interrupted by
signals. But using sigaction hangs the system. I've attached a test
application. And the recipe is:
1. compile the program testd.c
2. run testd in the background - testd &
3. send sigusr1 to testd process - kill -10 testd_pid
4. then the system will be hung.
The test application works if we use sighandler instead of sigaction
Bret
-----Original Message-----
From: owner-microblaze-uclinux@xxxxxxxxxxxxxx
[mailto:owner-microblaze-uclinux@xxxxxxxxxxxxxx] On Behalf Of John Williams
Sent: Thursday, June 08, 2006 11:02 PM
To: microblaze-uclinux@xxxxxxxxxxxxxx
Subject: Re: [microblaze-uclinux] 10 msec number of ticks bug..
Bret,
Bret Ketchum wrote:
> Speaking of timers and their handling, is it true that sigaction is
> not working in the microblaze flavor of uClinux, only sighandler? That
> signals (particularly alarm signals) abort io calls (poll/read/write) and
> are not restarted, or is that true when called with a timeout only? I'm
> using an old copy of uClinux out of CVS, maybe these items have been
looked
> into or that's just life. Thanks in advance for any hints.
Can you post some short test code that displays divergent behaviour on
mb-uclinux vs regular linux (or another arch-flavour of uclinux)?
Thanks,
John
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive :
http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/