- Boost - lists.boost.org

Updated Darwin tools
by Marshall Clow 06 Aug '04

06 Aug '04

Apple has released a new version of their developer tools, including an updated version of gcc. I have rerun the tests using the new gcc (3.3 build 1666). No major changes in the test results; a ICE while compiling one of the tests has been fixed. 30 failures (old compiler) vs. 28 (new compiler). -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.

1 0

Windows MSVC thread exit handler for staticly linked Boost.Thread
by Aaron W. LaFramboise 05 Aug '04

05 Aug '04

Following is an implementation of, and some comments on, a staticly linked Boost.Thread thread exit handler for MSVC. By the way, I appologize for talking so long to cough this up after posting teasing remarks about this months ago. Programming is presently a hobby and volunteer work for me, unfortunately. First, the handler itself: ---msvc_exit_handler.cpp--- // copyright disclaimed. ABSOLUTELY NO WARRANTY. #define WIN32_LEAN_AND_MEAN #include <windows.h> #define BOOST_THREAD_USE_LIB #include <boost/thread/thread.hpp> #include <boost/thread/tss.hpp> extern "C" BOOST_THREAD_DECL void on_process_exit(void); extern "C" BOOST_THREAD_DECL void on_thread_exit(void); namespace { // Force a TLS directory to be generated even when static TLS is not used. extern "C" int _tls_used; int dummy() { return _tls_used; } // Report thread and process detach events. void NTAPI tls_callback (PVOID, DWORD Reason, PVOID) { if(Reason == DLL_THREAD_DETACH) on_thread_exit(); else if(Reason == DLL_PROCESS_DETACH) { on_thread_exit(); on_process_exit(); } } // Add callback to the TLS callback list in TLS directory. #pragma data_seg(push, old_seg) #pragma data_seg(".CRT$XLB") DWORD tls_callback_ptr = (DWORD)tls_callback; #pragma data_seg(pop, old_seg) } // namespace // Indicate that TSS cleanup is implemented. extern "C" void tss_cleanup_implemented(void) { } ---EOF--- And a simple testcase: ---tss.cpp--- /* Uncomment the following to use _beginthread() to create theads instead * of CreateThread. */ // #define USE_BEGINTHREAD #include <iomanip> #include <iostream> #define WIN32_LEAN_AND_MEAN #include <windows.h> #include <process.h> #define BOOST_THREAD_USE_LIB #include <boost/thread/thread.hpp> #include <boost/thread/tss.hpp> class myclass { public: myclass(); ~myclass(); }; myclass::myclass() { std::cerr << "init: " << GetCurrentThreadId() << '\n'; } myclass::~myclass() { std::cerr << "fini: " << GetCurrentThreadId() << '\n'; } boost::thread_specific_ptr<myclass> value; #ifdef USE_BEGINTHREAD void thread_proc(void *) { value.reset(new myclass); } #else // USE_BEGINTHREAD DWORD WINAPI thread_proc(LPVOID) { value.reset(new myclass); return 0; } #endif // USE_BEGINTHREAD int main(int argc, char *argv[]) { value.reset(new myclass); for (int i=0; i<2; ++i) { #ifdef USE_BEGINTHREAD _beginthread(thread_proc, 0, 0); #else DWORD id; CreateThread(0, 0, thread_proc, 0, 0, &id); #endif } Sleep(100); } ---EOF--- I tested this on Microsoft Visual C++ Toolkit 2003 on Windows XP SP1, as follows: C:\aaronwl\cs\boost\tls\handler>cl /EHa /MT /I"C:\aaronwl\cs\boost\cvs\boost" tss.cpp msvc_exit_handler.cpp ... C:\aaronwl\cs\boost\tls\handler>tss init: 2976 init: 4080 fini: 4080 init: 4040 fini: 4040 fini: 2976 Note that thread termination is correctly reported for all of the main thread and the two extra threads. It is my guess that this mechanism will work correctly on all versions of i386 Windows since Windows 95 and Windows NT 3.51. However, I have not tested it exhaustively due to lack of access. This mechanism is required to work by the PECOFF specification, so I'd expect any compliant x86 PE loader to support it. It is also my guess that this method of generating a thread termination notification will work on any version of MSVC that generates "32-bit" Windows executables. Only part of this compiler support, as implemented, is mandated by PECOFF. While apparently unused, completely undocumented, and largely unknown, the TLS callback section support is very similar to the general CRT global initialization and finalization routines, which--while they are also undocumented--most likely can never be removed as it would break backward object compatibility. I would be suprised if this did not work on a future MSVC version. This method of catching thread termination shares a very serious flaw with the DllMain() method: the thread PTD has already been destroyed by the time this code runs. As you can see, everything appears to work fine despite this; however, this is only by chance. In some cases, I think the code will silently do the wrong thing. For example, output might be lost. There was some suggestion about re-creating the PTD temporarily. This sounds good to me, except I can not find a reasonable way to do this, as the ptd manipulation functions are not exported the MSVCRT runtime dll. It might be possible to create a ptd manually, but this seems very risky to me. There was also mention of some sort of runtime library floating point hook. I was unable to figure out anything about this; however, if this is possible, and the ptd is still valid when this hook is called, that method is probably superior. As far as I can tell, FlsCallback() offers no advantage with regards to the ptd issue. It is also called "too late." Another problem with this method is that it gets destructor order wrong. For example, in the case of termination of the main thread, global destructors will be called before the TSS destructors are. This also could lead to silent misbehavior. It is likely that a better method for handling termination of the main thread could be found, such as a global destructor. Note that, with this method, it doesn't particular matter how the thread was created. There will be no ptd regardless of whether the thread was created with _beginthread or not. I am working on code for the MinGW runtime that should be able to cause GCC on Windows to handle TSS destructors perfectly. I don't know anything about any of the other Windows compilers with regards to this issue. In summary, I beleive this is the best shot so far at implementing thread exit handlers when Boost.Thread is statically linked, despite its serious problems. It is possible that a way to mitigate these problems, or a superior alternative, could be found. Aaron W. LaFramboise

10 82

[regression] New CodeWarrior 8.3 tests
by Rene Rivera 05 Aug '04

05 Aug '04

In an effort to improve the situation with this toolset, and since it's the one I'm currently most interested in, I started running a set of regression tests for it on my machine. The results are the ones with "RSI" as the name. I'm running the tests on demand, that is whenever I do a CVS update, or otherwise don't have the machine tied. So if anyone wants a faster response than waiting the 12 or 24 hours for the other tests to run, email me (privately) and I'll try and do an update and run new tests as soon as possible. Also one important difference between this set of test and the rest, is that I run them in *release* mode. So regressions relating to optimizations show up, and also relating to NDEBUG being set. But more about that in another post :-) -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com - 102708583/icq

1 0

Invalid include in half_open_range.hpp
by Stefan Slapeta 05 Aug '04

05 Aug '04

...breaks half_open_range_test (utility) on all compilers. OK to commit? Stefan Index: half_open_range.hpp =================================================================== RCS file: /cvsroot/boost/boost/boost/half_open_range.hpp,v retrieving revision 1.5 diff -u -r1.5 half_open_range.hpp --- half_open_range.hpp 26 Jul 2004 00:31:58 -0000 1.5 +++ half_open_range.hpp 4 Aug 2004 14:21:29 -0000 @@ -12,7 +12,7 @@ #ifndef BOOST_HALF_OPEN_RANGE_HPP_ # define BOOST_HALF_OPEN_RANGE_HPP_ -# include <boost/counting_iterator.hpp> +# include <boost/iterator/counting_iterator.hpp> # include <functional> # include <cassert> # include <boost/operators.hpp>

3 6

[program_options] printing the variable map
by Jeff Garland 05 Aug '04

05 Aug '04

I'm writing a program with program_options (very cool and useful library, BTW) and I found myself wanting to print out the variable_map values for debugging purposes. Is there an easy way to do this? Also couple of documentation nits: 1) From the first example.... if (vm.count("help")) { std::cout << desc << "\n"; I had to read the code to figure out that variable_map inherits from std::map, and this is why you can call this. Documentation only says: class variables_map : : public boost::program_options::abstract_variables_map 2) In the 'Storage Component' section -- there's this: Let's consider an example: variables_map vm; store(parse_command_line(argc, argv, desc), vm); store(parse_config_file("example.cfg", desc), vm); finish(vm); .... Finally the call to notify function runs user-specified notify functions and stores values into regular variables, if needed. I assume 'finish' is supposed to be notify? I don't see any docs for finish. Jeff

2 1

build-monitor yet again
by Victor A. Wagner Jr. 05 Aug '04

05 Aug '04

I put the --monitored back in my script: ========================================== python regression.py setup --user=vawjr --toolsets=vc7.1,vc8.0 --bjam-toolset=vc7 python regression.py install --user=vawjr --toolsets=vc7.1,vc8.0 --bjam-toolset=vc7 --incremental python regression.py test --user=vawjr --toolsets=vc7.1,vc8.0 --incremental --monitored python regression.py collect-logs --user=vawjr --runner=RudbekAssociates --incremental --comment comment.html python regression.py upload-logs --runner=RudbekAssociates ========================================== I took a couple of "pictures" of the task manager one before I went to bed last night and when I got up this morning they can be found at ftp://rudbek.com/pub/boost I've modified regression.py to: ========================================= utils.system( [ 'start /belownormal %s bjam.exe %d >build_monitor.log 2>&1' % ( build_monitor_path, timeout*60 ) ] ) ========================================= unfortunately build_monitor.log is 0 length this morning I believe that the the dir of the logfiles shows that the IRC client wasn't all shut down at the same time, it seems to have taken several minutes I thought I'd taken a before picture of the desktop, but I apparently don't understand my grabber as well as I thought. I'll take one now that should resemble a lot the one from before. I trust this evidence will put to rest whether build_monitor actually arbitrarily stops probrams with NO regard as to who or what started them. Victor A. Wagner Jr. http://rudbek.com The five most dangerous words in the English language: "There oughta be a law"

1 0

shared_ptr doc issue
by David Abrahams 05 Aug '04

05 Aug '04

In the constructor documentation, it seems that "Notes" is used to document what really are preconditions, e.g.: "p must be a pointer to an object that was allocated via a C++ new expression or be 0" Normally, "notes" are considered to be non-normative in the standard. I am trying to update a document on exception safety and it would be a big help if all the preconditions appeared in the "Requires" clause. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com

2 3

boost\libs\python\build\VisualStudio workspace
by Max Khesin 05 Aug '04

05 Aug '04

VS6 refuses to open the .dsw & .dsp from CVS. Char. diff to v 31.0 shows that the files are equivalent - have they been set to binary or something? thanks, max. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.

2 1

const_pointer_cast for shared_ptr
by Colin Rafferty 05 Aug '04

05 Aug '04

I would like to propose adding const_pointer_cast<> to shared_ptr, in exactly the same way that there is dynamic_pointer_cast<> and static_pointer_cast<>. I am surprised that it is missing. Is there a reason for that? If not, I will submit a patch that implements this. Thanks. -- Colin

5 4

[Boost-bugs] [ boost-Bugs-1003889 ] tokenizer and signed char
by SourceForge.net 05 Aug '04

05 Aug '04

Bugs item #1003889, was opened at 2004-08-05 04:41 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1003889&group_… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: tokenizer and signed char Initial Comment: boost::tokenizer incorrect works on platforms on which plain char is signed. For example, at least in boost::char_delimiters_separator::is_nonret should be explicit conversion from char type to int type. Something like this std::isspace (std::char_traits<Char>::to_int_type(E)). Minimal reproducer for this issue which uses Russian letters results in assert in MSVC 7.1: // cl /Zi /MDd -D_DEBUG test.cpp #include <boost\tokenizer.hpp> #include <string> #include <iostream> using namespace std; using namespace boost; int main() { string s = "Здравствуй мир!"; tokenizer<> tok(s); for (tokenizer<>::iterator beg=tok.begin(); beg! =tok.end();++beg) { cout << *beg << "\n"; } } ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1003889&group_… ------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0