Mail Archives: djgpp/2000/12/17/21:27:13
On Sun, 17 Dec 2000 21:19:37 +0200, "Eli Zaretskii"
<eliz AT is DOT elta DOT co DOT il> wrote:
>The DJGPP port of LWP is mentioned in section 22.4 of the DJGPP FAQ
>list. Are you using a ported version? If not, it's quite possible
>that the code you are using isn't supposed to work with DJGPP.
Hi and thanks for replying ! The version of LWP is indeed meant
to be used with djgpp. And specifically told to work with Win95
(and W98, I guess).
>What does the program do in each thread? Due to the way signals are
>implemented in DJGPP, some activities, such as DOS function calls,
>stop threading until the DOS call returns.
The threads just print their PID number and delay a while (by
busyloop).
Printing with printf is handled with semaphore, so that there should
be no re-entrancy problems. No other library or DOS functions are
called.
>Ouch, Windows. I'd suggest to try in DOS mode first, with CWSDPMI.
>Windows has some nasty tricks as far as timer interrupt is concerned
Works even worse in DOS - the SIGSEGV hits immediately.
I think that maybe the stack frame set up by SIGILL (which the
LWP uses as scheduling interrupt) is set up differently in the
current djgpp version than in the one LWP was tested with. Too bad
I can't find any newer version of LWP. Maybe I should start looking
for some other threading package.
br
Tuukka
- Raw text -