From: "OiSyN" Newsgroups: comp.os.msdos.djgpp Subject: alarm signal for multithreading Date: Sat, 26 Feb 2000 19:24:58 +0100 Message-ID: <951589170.6346.0.pluto.d4ee0fa5@news.demon.nl> NNTP-Posting-Host: x-project.demon.nl X-NNTP-Posting-Host: x-project.demon.nl:212.238.15.165 X-Trace: news.demon.nl 951589170 pluto:6346 NO-IDENT x-project.demon.nl:212.238.15.165 X-Complaints-To: abuse AT nl DOT demon DOT net X-Newsreader: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Lines: 30 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Hi! The answers of my previous post (Multithreading dmpi, posted yesterday on this newsgroup) have brought up a new question... I set my a signal handler with signal (int, void(*)()). That handler contains some taskswitching code, so the handler never returns, but jumps to another code section. But if the handler doesn't return, another signal can't be caught. I think because djgpp thinks that the signal isn't completely handled, since it doesn't return... Does someone know how to point out to DJGPP that the signal IS handled, so I can catch another SIGALRM (or another signal) later on? By the way, what's the calling convention for a signal? Is it like an interrupt routine? I hope it is, 'cause I need the flags which are pushed by an interrupt call. Or does someone know what exception is raised when an alarm signal is raised? Then I can hook the exception handler and have the flags I need on the stack, and I don't have to bother about my first problem (signals disabled). Thanx! OiSyN -- Hi, I'm a signature virus. plz set me as your signature and help me spread :)