tcdrain won't work?
Hi, I tried to use tcdrain to make sure that all characters are sent via a COM port but it seems that it won't work in about 50% of the calls to it, i.e. tcdrain returns before all characters are sent via sio.c. Has anyone noticed that effect? I tried to understand how it works. Apparently tty.c operates in ttywait() and ttwwakeup() on the output queue size in tp-t_outq.c_cc and TS_BUSY in tp-t_state (?). I can't find any piece of code filling tp-t_outq.c_cc with other values than 0. And sio.c seems to not set TS_BUSY in tp if outq.c_cc is not 0. Is it simply unimplemented or have I missed the point? Thanks in advance! Titus To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: GCC Upgrade?
David O'Brien wrote: Monday. GCC 2.95.3 will hi 4-STABLE after April 1st. Heck, April 1st might actually be the best day to do it. So if RELENG_4 is unfrozen by then, that's when I'll MFC it. ;) Hi, I just posted the question in another thread: Since at least aug. 2000 (according to the mailing list archives) the exception handling in base system g++ is broken (at least for multithreaded programs) My questions were: What causes the bug in exception handling? Why does the packaged g++ work? And: will the next release of freebsd be ok? regards titus To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: GCC Upgrade?
David O'Brien wrote: On Mon, Mar 19, 2001 at 02:54:52PM +0100, Titus von Boxberg wrote: Since at least aug. 2000 (according to the mailing list archives) the exception handling in base system g++ is broken (at least for multithreaded programs) I am not aware of exception handling being broken (more so than in 4.x). g++ in the base is nok, as the package it's ok. Can you point me to a PR, or send me a _small_ sample program? Sorry, I don't have yet isolated the problem. But this link seems to describe exactly the same problem. "http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=298763+300854+ /usr/local/www/db/text/2000/freebsd-hackers/2716.freebsd-hackers" you can search for "DWARF AND exception"; then you'll find the links. I'm using omniORB, and on their home page you can find a hint in the docs describing the same thing (but with g++ on a AIX/RS6000). Before end of april I cannot investigate the problem any further. please let me know by then if I may help you with that problem. regards titus To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
c++ exceptions with pthreads
Hi, I just read your reply in the hackers mailing list regarding c++ exceptions. Does that mean that now (or from release 4.3 on) the base system g++ is bugfixed regarding SIGSEGVs with c++ exceptions? What causes the bug in exception handling? Why does the packaged g++ work? Thanks in advance regards titus To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Unicode on FreeBSD
Alex Belits wrote: Anyone who has anything to do with the Internet must deal with UTF-8: "Protocols MUST be able to use the UTF-8 charset, which consists of the ISO 10646 coded character set combined with the UTF-8 character encoding scheme, as defined in [10646] Annex R (published in Amendment 2), for all text." RFC 2277 This is not approved by ANYONE but a bunch of "unificators". It never was widely discussed, and affected people never had a chance to give any input. This is the same kind of "standard documents" that ITU issues by dozens. I don't guess what meaning could be transferred by the quotation marks around standard documents. As far as I know (especially the Q, X and I series), the ITU-T produces quite good standards that are widely, if not globally accepted (just think about V.34 or V.29, V.17, T.30 and so on). Check'em out and try to send a fax. It works globally. Quite astonishing, isn't it? Or, if that isn't sufficient, you may use the same software to connect to X.25 networks all around the world. You can establish modem connections around the world (after Bell labs standards ceased to exist). You can connect the same ISDN equipment virtually everywhere in Europe to the trunk line... If Unicode is equally well accepted, there should be no problem with it. Bye, Titus [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Pthread blocking I/O
Hi, I use two threads to do I/O for a process. The I/O takes place either on a socket or an I/O device (com port) file descriptor. Apparently it is not possible to shutdown those threads from a third thread, neither using close nor shutdown(2) for the socket I/O if the threads are blocked during read. What methods can one use to unblock such a blocked-on-read thread? Thanks, TITUS To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
