Bug 10346 - iBCS bug that produces "SIG: sigpending lied" in Foxpro 2.6 for Unix
iBCS bug that produces "SIG: sigpending lied" in Foxpro 2.6 for Unix
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
4.2
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Alan Cox
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-03-25 16:24 EST by Dennis Allen
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-12-15 22:02:11 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Tested and working patch for kernel-2.2.16-3.src.rpm (355 bytes, patch)
2000-08-15 17:25 EDT, Jan Carlson
no flags Details | Diff

  None (edit)
Description Dennis Allen 2000-03-25 16:24:52 EST
To get SCO Foxpro 2.6 for Unix to work on a RedHat 6.0 Linux, you must
load the iBCS module [insmod iBCS.o].

When FPU produces a bell, you will see several "SIG: sigpending lied"
messages.  This message is from a bug in the iBCS component of the Linux
kernel. Well, Piotr Kasprzyk actually found this bug and showed me how to
fix it.

vi /usr/src/linux/ibcs/iBCSemul/signal.c

In the file signal.c find function deactivate_signal(), around line 95.
You'll need to add the line:

          recalc_sigpending(task);

This function should then look like:

     void
     deactivate_signal(struct task_struct *task, int signum)
     {
             spin_lock_irq(&task->sigmask_lock);
             sigdelset(&task->signal, signum);
          recalc_sigpending(task);
             spin_unlock_irq(&task->sigmask_lock);
     }
Comment 1 Jan Carlson 2000-08-15 17:25:03 EDT
Created attachment 2523 [details]
Tested and working patch for kernel-2.2.16-3.src.rpm
Comment 2 Alan Cox 2002-12-15 22:02:11 EST
xabi replaced ibcs2

Note You need to log in before you can comment on or make changes to this bug.