Hey all,

I have been trying to port some code to FreeBSD which currently runs under
Linux (and to some degree, Solaris).  Since I'm a longtime FreeBSD user,
I'm pretty excited to get a chance to port to FreeBSD.

The program I'm working on uses both POSIX threads and ISO C++ (including
templates, exceptions, etc.), so I needed information about the current
state of such things under FreeBSD.  However, there wasn't any "one-stop"
documentation I could find about the current state of everything.

As a result, I ended up writing a brief text document which describes what
I found out about threads (C++ and threads is only mentioned briefly).  
If anyone who knows about the state of the FreeBSD threads implementation
could go through it and check it for factual errors, missing bits, etc.
then that would be great.

Included at the end of the document is a little bit about the planned
implementation using scheduler activations for -CURRENT, but that section
is almost totally just posts copied from the mailing list archives.

I would be happy to contribute this information to the Documentation
project if that would be preferable.

The URL for the document is

        http://www.idiom.com/~bko/bsd/freebsd-threads.txt


A few quick questions:

1.  I had seen an email in the mailing list archives which asserted that
C++ exceptions have been broken since August 1999 in the multithread case
-- does anyone know what the status in 4.1-STABLE and -CURRENT are?  I've
managed to get the code to compile under FreeBSD, but it crashes quite
rapidly after this, and I'm wondering if it's because of an exception
being thrown.  This is under 4.1-RELEASE.


2.  Sometimes, the programs crash at startup, but not always.  I seem to
recall a recent discussion about the loader not being multi-thread safe --
was this fixed in time for 4.1-RELEASE ?

Thanks,

-- 
bryan k ogawa  <[EMAIL PROTECTED]>   http://www.primenet.com/~bkogawa/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Reply via email to