Turbo C 1.5 ssignal() function

Thread View: comp.os.msdos.programmer

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Mark Holbrook Wed, 08 Aug 1990 18:16

#1826

Author: Mark Holbrook
Date: Wed, 08 Aug 1990 18:16

21 lines
1455 bytes

The Turbo C version 1.5 ssignal() function seems to be like the
signal() function in other C compilers, but doesn't seem to intercept
signals the way signal() does (at least for ssignal() on my PC vs.
signal() on a real UNIX machine).  For example, if I define a routine
"fpe" to handle floating point exceptions, then use ssignal(SIGFPE,
fpe) to establish fpe() as the handler, and then execute, say, a floating
point divide-by-zero, I get the standard Turbo C error message rather
than whatever fpe() does.

Any advice?  Do I need 2.0?  Is there something I'm not doing right?

(The above question comes from trying to get gnuplot v. 2.0 compiled
and running on a 286 clone with Hercules graphics.  Some #ifdef __TURBOC__
code includes calls to signal(), which I (TC 1.5) don't have.)

Mark Holbrook

Alliant Computer Systems Corporation     Phone: (508) 486-1262
1 Monarch Drive                            FAX: (508) 486-1398
Littleton, MA 01460                     E-mail: holbrook@alliant.COM

Re: Turbo C 1.5 ssignal() function

#1829

Author: Eric Gisin
Date: Thu, 09 Aug 1990 12:08

4 lines
715 bytes

Gsignal and ssignal are a software signal package derived
from System V.  Ssignal installs a handler, and gsignal
generates a signal. These signals are never generated by
faults, traps, or interrupts. That's how it worked in System V.

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads