August 2007 - Boost-users - lists.preview.boost.org

[Fwd: boost serialization excessive warning messages]
by Fei Liu 16 Aug '07

16 Aug '07

1 0

Boost regex Java Regex package compatibility
by Sudarshan Gaikaiwari 16 Aug '07

16 Aug '07

Hello Boost Experts Here is my situation. Users write regular expressions which act as input to our programs and are used to perform matches. Currently the code base is Java and uses the java.util.regex package to handle regular expressions. I need to convert this code to C++ and intend to use boost regex. How compatible is boost regex with Java regex? I have looked at Java regex documentation here http://java.sun.com/j2se/1.5.0/docs/api/java/util/regex/Pattern.html to note the differences between Java regex and Perl 5 regexs. Are these the only with boost regex also? -- Sudarshan Gaikaiwari www.sudarshan.org sudarshan(a)acm.org

2 1

exceptions from regexp library usage
by Venkat Rangan 16 Aug '07

16 Aug '07

Hi, I get the following exception while using a boost regexp matching libraries (with Windows Visual Studio, 7.1 environment). Setup: static RegexClass::RegularExpression re_exp; bool CMyclass::parseExpression(string expression) { LoggerPtr logger = Logger::getRootLogger(); ostringstream oss; RegexClass::RegularExpression *re = &re_exp; re->Expression = expression; RegexClass::RegularExpression::ExpressionErrorCode eec = re->ParseExpression(); if (eec == RegexClass::RegularExpression::REG_NOERROR) { oss << "Parse successful: " << expression; logger->info(oss.str()); return true; } ... } Matching call: bool CMyClass::matchSpec(RegexClass::RegularExpression *pRe, const char *stringToMatch) { pRe->SetStringToMatch(stringToMatch); if (pRe->Match()) { return true; } return false; } Exception while using expression matcher on Windows Server 2003 Platforms: Exception Stack Trace 0x0343c900 0x00457374 boost::re_detail::reg_grep2<boost::re_detail::grep_search_predicate<std: :basic_string<char,std::char_traits<char>,std::allocator<char> >::iterator,boost::detail::allocator<char> >,std::basic_string<char,std::char_traits<char>,std::allocator<char> >::iterator,char,boost::regex_traits<char>,boost::detail::allocator<char >,boost::detail::allocator<char> > 0x00000044 0x0343c924 0x0045a65b boost::regex_search<std::basic_string<char,std::char_traits<char>,std::a llocator<char>>::iterator,boost::detail::allocator<char>,char,boost::reg ex_traits<char>,boost::detail::allocator<char> > 0x0000003b 0x0343c970 0x0045ae66 RegexClass::RegularExpression::Match 0x000001c6 Sometimes, I get the following exception: Stack Trace 0x037dc938 0x0045db6e RegexClass::RegularExpressionPimpl::GetMatchingInformation 0x0000027e 0x037dc970 0x0045af19 RegexClass::RegularExpression::Match 0x00000279 0x037dc9a0 0x004370b1 CMyClass::matchSpec 0x00000091 at myclass.cpp(349) Any help would be much appreciated. Thanks.

2 1

Link errors using Boost & STLPort with VC8
by Jason Ivey 16 Aug '07

16 Aug '07

I am attempting to compile and link a small test application using STLPort_5.1.3, boost_1_34_1 and MSVC8 sp1. Everything works fine when I don't have to link against any boost libraries. To test linking against the boost static libraries I wrote a simple little test app that used the boost::regex library and ran into errors. I am not completely sure that this is a boost issue but since I can compile and link programs without any problems that don't use boost binaries I wasn't sure of who else to turn to. The linker error I am getting is: 1>LINK : fatal error LNK1104: cannot open file 'stlportstld_x.5.1.lib' The problem is that all of the stlport libraries are named stlportstld.5.1.lib or similar. I did try to just rename the library to make it match but, of course, I got a boat load of unresolved external linker errors pointing to names such as "stlpdx_std::basic_string." Looking at a dumpbin output of the actual regex library it is linking against, libboost_regex-vc80-mt-sgdp-1_34_1.lib, I found linker directives of the form: /DEFAULTLIB:"stlportstld_x.5.1.lib" /DEFAULTLIB:"libcpmtd" /DEFAULTLIB:"LIBCMTD" /DEFAULTLIB:"OLDNAMES" I couldn't find anywhere that boost had put those directives in the libraries but I could be missing something so I also did a dumpbin of one of the stlport libraries, stlportd_static.5.1.lib, and only found the following linker directives: /DEFAULTLIB:"LIBCMTD" /DEFAULTLIB:"OLDNAMES" I have to believe there are at least a few companies out there who have replaced the shipping MSVC STL for testing purposes, if for no other reason, and are also using Boost so hopefully I'm just missing something obvious. Below are the steps I followed to compile both sets of libraries and the test application. Let me know if anything appears to be off or if there is simply a better/easier way. Thanks, Jason Ivey Open command prompt and run: "%VS80COMNTOOLS%\vsvars32.bat" STLPort_5.1.3 build\lib\configure -c msvc8 nmake /fmsvc.mak install Boost_1_34_1 edit tools\build\v2\user-config.jam added line 45 with using stlport : : d:\\build\\stlport\\stlport d:\\build\\stlport\\lib ; bjam --toolset=msvc stdlib=stlport --with-regex stage Build Test Application set include=d:\build\stlport\stlport;D:\build\boost_1_34_1;%include% set lib=d:\build\stlport\lib;D:\build\boost_1_34_1\stage\lib;%lib% call "%VS80COMNTOOLS%\..\IDE\devenv.exe" /useenv

2 2

function/bind - passing function pointer to C API
by Nicholas Yue 16 Aug '07

16 Aug '07

Hi, I am attempting to use Boost bind and function to help me pass a member function as a function pointer to the GLUT C-library. I have difficulty understanding the usage of bind and function in the Boost library. When I attempt to pass what I thought was a function pointer, the compiler indicated that it is actually not a function pointer. class MyGlut { public: MyGlut(); virtual ~MyGlut(); void loop(int argc, char **argv); void draw(void); void displayFunc(boost::function<void()> func); private: boost::function<void()> display_callback; }; void MyGlut::displayFunc(boost::function<void()> func) { glutDisplayFunc(func); // ERROR IN COMPILATION } void MyGlut::loop(int argc, char **argv) { glutInit(&argc,argv); glutInitDisplayMode(GLUT_RGB | GLUT_DOUBLE | GLUT_DEPTH | GLUT_MULTISAMPLE); glutCreateWindow("Hello World"); //glutDisplayFunc(redraw); // Original way to pass C-function pointer displayFunc( boost::bind(&MyGlut::draw, *this) ); } Regards

2 1

Need ideas...
by Noah Roberts 16 Aug '07

16 Aug '07

I am trying to generalize the concept of putting database data into boost::tuple objects. I'm thinking syntax similar to something like so: typedef boost::tuple<int, double, std::string> row; row r = SqlQuery<row>::run_query(db, "select * from x"); I imagine something like so being contained in the processing: TUPLE t; ... t.get<X>() = boost::lexical_cast< typename boost::tuples::element<X,TUPLE>::type >(data[X]); // data is char ** Where X is the index of the element and the entire tuple is iterated in this manner. I thought maybe there would be something in MPL that could help but I'm not seeing it. Anyone got any bright ideas?

5 7

BOOST pass an object to python code
by alex＠gorex.com.hk 16 Aug '07

16 Aug '07

Hello, I am new in this list. I would like to ask a quesiton about the linkage between BOOST and Python. I want to use C++ to trigger a Python code so that when I change anything inside Python, my C++ can know the changes and get the result back. So how can I pass an object from C++ to Python? and return the result? Here is the code that embedded the Class. class CppClass { public: int getNum() { return 7; } }; #include <boost/python.hpp> using namespace boost::python; int main( int argc, char ** argv ) { try { Py_Initialize(); object main_module(( handle<>(borrowed(PyImport_AddModule("__main__"))))); object main_namespace = main_module.attr("__dict__"); main_namespace["CppClass"] = class_<CppClass>("CppClass") .def("getNum",&CppClass::getNum); handle<> ignored(( PyRun_String( ""cpp = CppClass()\n" "print cpp.getNum()\n"", Py_file_input, main_namespace.ptr(), main_namespace.ptr() ) )); } catch( error_already_set ) { PyErr_Print(); } } Thanks

1 0

[OT] Stroustrup video on slashdot
by Christian Henning 15 Aug '07

15 Aug '07

Hi there, some of you might be interested in watching his talk. http://it.slashdot.org/it/07/08/13/0818238.shtml I found this interview with Bjarne quite interesting: ----------- Interviewer: Well, it's been a few years since you changed the world of software design, how does it feel, looking back? Stroustrup: Actually, I was thinking about those days, just before you arrived. Do you remember? Everyone was writing 'C' and, the trouble was, they were pretty damn good at it. Universities got pretty good at teaching it, too. They were turning out competent - I stress the word 'competent' - graduates at a phenomenal rate. That's what caused the problem. Interviewer: Problem? Stroustrup: Yes, problem. Remember when everyone wrote Cobol? Interviewer: Of course, I did too Stroustrup: Well, in the beginning, these guys were like demi-gods. Their salaries were high, and they were treated like royalty. Interviewer: Those were the days, eh? Stroustrup: Right. So what happened? IBM got sick of it, and invested millions in training programmers, till they were a dime a dozen. Interviewer: That's why I got out. Salaries dropped within a year, to the point where being a journalist actually paid better. Stroustrup: Exactly. Well, the same happened with 'C' programmers. Interviewer: I see, but what's the point? Stroustrup: Well, one day, when I was sitting in my office, I thought of this little scheme, which would redress the balance a little. I thought 'I wonder what would happen, if there were a language so complicated, so difficult to learn, that nobody would ever be able to swamp the market with programmers? Actually, I got some of the ideas from X10, you know, X windows. That was such a bitch of a graphics system, that it only just ran on those Sun 3/60 things. They had all the ingredients for what I wanted. A really diculously complex syntax, obscure functions, and pseudo-OO structure. Even now, nobody writes raw X-windows code. Motif is the only way to go if you want to retain your sanity. Interviewer: You're kidding...? Stroustrup: Not a bit of it. In fact, there was another problem. Unix was written in 'C', which meant that any 'C' programmer could very easily become a systems programmer. Remember what a mainframe systems programmer used to earn? Interviewer: You bet I do, that's what I used to do. Stroustrup: OK, so this new language had to divorce itself from Unix, by hiding all the system calls that bound the two together so nicely. This would enable guys who only knew about DOS to earn a decent living too. Interviewer: I don't believe you said that... Stroustrup: Well, it's been long enough, now, and I believe most people have figured out for themselves that C++ is a waste of time but, I must say, it's taken them a lot longer than I thought it would. Interviewer: So how exactly did you do it? Stroustrup: It was only supposed to be a joke, I never thought people would take the book seriously. Anyone with half a brain can see that object-oriented programming is counter-intuitive, illogical and inefficient. Interviewer: What? Stroustrup: And as for 're-useable code' - when did you ever hear of a company re-using its code? Interviewer: Well, never, actually, but... Stroustrup: There you are then. Mind you, a few tried, in the early days. There was this Oregon company - Mentor Graphics, I think they were called - really caught a cold trying to rewrite everything in C++ in about '90 or '91. I felt sorry for them really, but I thought people would learn from their mistakes. Interviewer: Obviously, they didn't? Stroustrup: Not in the slightest. Trouble is, most companies hush-up all their major blunders, and explaining a $30 million loss to the shareholders would have been difficult. Give them their due, though, they made it work in the end. Interviewer: They did? Well, there you are then, it proves O-O works. Stroustrup: Well, almost. The executable was so huge, it took five minutes to load, on an HP workstation, with 128MB of RAM. Then it ran like treacle. Actually, I thought this would be a major stumbling-block, and I'd get found out within a week, but nobody cared. Sun and HP were only too glad to sell enormously powerful boxes, with huge resources just to run trivial programs. You know, when we had our first C++ compiler, at AT&T, I compiled 'Hello World', and couldn't believe the size of the executable. 2.1MB Interviewer: What? Well, compilers have come a long way, since then. Stroustrup: They have? Try it on the latest version of g++ - you won't get much change out of half a megabyte. Also, there are several quite recent examples for you, from all over the world. British Telecom had a major disaster on their hands but, luckily, managed to scrap the whole thing and start again. They were luckier than Australian Telecom. Now I hear that Siemens is building a dinosaur, and getting more and more worried as the size of the hardware gets bigger, to accommodate the executables. Isn't multiple eritance a joy? Interviewer: Yes, but C++ is basically a sound language. Stroustrup: You really believe that, don't you? Have you ever sat down and worked on a C++ project? Here's what happens: First, I've put in enough pitfalls to make sure that only the most trivial projects will work first time. Take operator overloading. At the end of the project, almost every module has it, usually, because guys feel they really should do it, as it was in their training course. The same operator then means something totally different in every module. Try pulling that lot together, when you have a red or so modules. And as for data hiding. God, I sometimes can't help laughing when I hear about the problems companies have making their modules talk to each other. I think the word 'synergistic' was specially invented to twist the knife in a project manager's ribs. Interviewer: I have to say, I'm beginning to be quite appalled at all this. You say you did it to raise programmers' salaries? That's obscene. Stroustrup: Not really. Everyone has a choice. I didn't expect the thing to get so much out of hand. Anyway, I basically succeeded. C++ is dying off now, but programmers still get high salaries - especially those poor devils who have to maintain all this crap. You do realise, it's impossible to maintain a large C++ software module if you didn't actually write it? Interviewer: How come? Stroustrup: You are out of touch, aren't you? Remember the typedef? Interviewer: Yes, of course. Stroustrup: Remember how long it took to grope through the header files only to find that 'RoofRaised' was a double precision number? Well, imagine how long it takes to find all the implicit typedefs in all the Classes in a major project. Interviewer: So how do you reckon you've succeeded? Stroustrup: Remember the length of the average-sized 'C' project? About 6 months. Not nearly long enough for a guy with a wife and kids to earn enough to have a decent standard of living. Take the same project, design it in C++ and what do you get? I'll tell you. One to two years. Isn't that great? All that job security, just through one mistake of judgement. And another thing. The universities haven't been teaching 'C' for such a long time, there's now a shortage of decent 'C' programmers. Especially those who know nything about Unix systems programming. How many guys would know what to do with 'malloc', when they've used 'new' all these years - and never bothered to check the return code. In fact, most C++ programmers throw away their return codes. Whatever happened to good ol' '-1'? At least you knew you had an error, without bogging the thing down in all that 'throw' 'catch' 'try' stuff. Interviewer: But, surely, inheritance does save a lot of time? Stroustrup: Does it? Have you ever noticed the difference between a 'C' project plan, and a C++ project plan? The planning stage for a C++ project is three times as long. Precisely to make sure that everything which should be inherited is, and what shouldn't isn't. Then, they still get it wrong. Whoever heard of memory leaks in a 'C' program? Now finding them is a major industry. Most companies give up, and send the product out, knowing it leaks like a sieve, simply to avoid the expense of tracking them all down. Interviewer: There are tools... Stroustrup: Most of which were written in C++. Interviewer: If we publish this, you'll probably get lynched, you do realise that? Stroustrup: I doubt it. As I said, C++ is way past its peak now, and no company in its right mind would start a C++ project without a pilot trial. That should convince them that it's the road to disaster. If not, they deserve all they get. You know, I tried to convince Dennis Ritchie to rewrite Unix in C++. Interviewer: Oh my God. What did he say? Stroustrup: Well, luckily, he has a good sense of humor. I think both he and Brian figured out what I was doing, in the early days, but never let on. He said he'd help me write a C++ version of DOS, if I was interested. Interviewer: Were you? Stroustrup: Actually, I did write DOS in C++, I'll give you a demo when we're through. I have it running on a Sparc 20 in the computer room. Goes like a rocket on 4 CPU's, and only takes up 70 megs of disk. Interviewer: What's it like on a PC? Stroustrup: Now you're kidding. Haven't you ever seen Windows '95? I think of that as my biggest success. Nearly blew the game before I was ready, though. Interviewer: You know, that idea of a Unix++ has really got me thinking. Somewhere out there, there's a guy going to try it. Stroustrup: Not after they read this interview. Interviewer: I'm sorry, but I don't see us being able to publish any of this. Stroustrup: But it's the story of the century. I only want to be remembered by my fellow programmers, for what I've done for them. You know how much a C++ guy can get these days? Interviewer: Last I heard, a really top guy is worth $70 - $80 an hour. Stroustrup: See? And I bet he earns it. Keeping track of all the gotchas I put into C++ is no easy job. And, as I said before, every C++ programmer feels bound by some mystic promise to use every damn element of the language on every project. Actually, that really annoys me sometimes, even though it serves my original purpose. I almost like the language after all this time. Interviewer: You mean you didn't before? Stroustrup: Hated it. It even looks clumsy, don't you agree? But when the book royalties started to come in... well, you get the picture. Interviewer: Just a minute. What about references? You must admit, you improved on 'C' pointers. Stroustrup: Hmm. I've always wondered about that. Originally, I thought I had. Then, one day I was discussing this with a guy who'd written C++ from the beginning. He said he could never remember whether his variables were referenced or dereferenced, so he always used pointers. He said the little asterisk always reminded him. Interviewer: Well, at this point, I usually say 'thank you very much' but it hardly seems adequate. Stroustrup: Promise me you'll publish this. My conscience is getting the better of me these days. Interviewer: I'll let you know, but I think I know what my editor will say. Stroustrup: Who'd believe it anyway? Although, can you send me a copy of that tape? Interviewer: I can do that.

3 2

Having trouble with boost thread library
by Fei Liu 15 Aug '07

15 Aug '07

#ifndef UTILS_NETWORK_TCP_CONNECTION_HPP #define UTILS_NETWORK_TCP_CONNECTION_HPP namespace utils{ namespace thread{ template <typename shared_obj_type, typename thread_pool_type, typename serverlet_type> class tcp_connection{ private: int newsockfd; shared_obj_type obj; thread_pool_type pool; serverlet_type serverlet; bool initialized_; public: tcp_connection() : initialized_ (false) {} tcp_connection(int newsockfd, shared_obj_type obj, thread_pool_type pool, serverlet_type serverlet) : newsockfd(newsockfd), obj(obj), pool(pool), serverlet(serverlet), initialized_(true) { } bool initialized() { return initialized_; } bool initialize(int newsockfd, shared_obj_type obj, thread_pool_type pool, serverlet_type serverlet); void operator ()(); }; template <typename shared_obj_type, typename thread_pool_type, typename serverlet_type> bool tcp_connection<shared_obj_type, thread_pool_type, serverlet_type>::initialize (int newsockfd, shared_obj_type obj, thread_pool_type pool, serverlet_type serverlet) { this->newsockfd = newsockfd; this->obj = obj; this->pool = pool; this->serverlet = serverlet; initialized_ = true; return initialized_; } template <typename shared_obj_type, typename thread_pool_type, typename serverlet_type> void tcp_connection<shared_obj_type, thread_pool_type, serverlet_type>::operator() () { //if(initialized_) serverlet_type(newsockfd, obj); <---- causes error pool->release(); } } } #endif main.cpp: provides definition of serverlet_type #include "utils/thread/tcp_server.hpp" #include "utils/thread/thread_pool.h" #include <boost/shared_ptr.hpp> #include <vector> #include <iostream> typedef std::vector<int> shared_obj_type; typedef boost::shared_ptr<boost_thread::thread_pool> thread_pool_type; typedef void (*serverlet_type)(int, shared_obj_type); void servlet(int sock, shared_obj_type ){ std::cout << "got a new socket for a new connection: " << sock << std::endl; } int main(){ shared_obj_type x; thread_pool_type p( new boost_thread::thread_pool(20) ); utils::thread::tcp_server<shared_obj_type, thread_pool_type, serverlet_type> server; server.initialize(x, p, servlet, 10000, 5); boost::thread s(server); s.join(); } /root/cpp-utils-header-lib/include/utils/thread/tcp_connection.hpp: In member function `void utils::thread::tcp_connection<shared_obj_type, thread_pool_type, serverlet_type>::operator()() [with shared_obj_type = shared_obj_type, thread_pool_type = thread_pool_type, serverlet_type = void (*)(int, shared_obj_type)]': /usr/include/boost/function/function_template.hpp:155: instantiated from `static void boost::detail::function::void_function_obj_invoker0<FunctionObj, R>::invoke(boost::detail::function::function_buffer&) [with FunctionObj = utils::thread::tcp_connection<shared_obj_type, thread_pool_type, void (*)(int, shared_obj_type)>, R = void]' /usr/include/boost/function/function_template.hpp:368: instantiated from `void boost::detail::function::basic_vtable0<R, Allocator>::init(FunctionObj, boost::detail::function::function_obj_tag) [with FunctionObj = utils::thread::tcp_connection<shared_obj_type, thread_pool_type, void (*)(int, shared_obj_type)>, R = void, Allocator = std::allocator<boost::function_base>]' /usr/include/boost/function/function_template.hpp:298: instantiated from `void boost::detail::function::basic_vtable0<R, Allocator>::init(F) [with F = utils::thread::tcp_connection<shared_obj_type, thread_pool_type, void (*)(int, shared_obj_type)>, R = void, Allocator = std::allocator<boost::function_base>]' /usr/include/boost/function/function_template.hpp:277: instantiated from `boost::detail::function::basic_vtable0<R, Allocator>::basic_vtable0(F) [with F = utils::thread::tcp_connection<shared_obj_type, thread_pool_type, void (*)(int, shared_obj_type)>, R = void, Allocator = std::allocator<boost::function_base>]' /usr/include/boost/function/function_template.hpp:655: instantiated from `void boost::function0<R, Allocator>::assign_to(Functor) [with Functor = utils::thread::tcp_connection<shared_obj_type, thread_pool_type, void (*)(int, shared_obj_type)>, R = void, Allocator = std::allocator<boost::function_base>]' /usr/include/boost/function/function_template.hpp:513: instantiated from `boost::function0<R, Allocator>::function0(Functor, typename boost::enable_if_c< boost::type_traits::ice_not< boost::is_integral<Functor>::value>::value, int>::type) [with Functor = utils::thread::tcp_connection<shared_obj_type, thread_pool_type, void (*)(int, shared_obj_type)>, R = void, Allocator = std::allocator<boost::function_base>]' /root/cpp-utils-header-lib/include/utils/thread/tcp_server.hpp:107: instantiated from `void utils::thread::tcp_server<shared_obj_type, thread_pool_type, serverlet_type, accept_fail_policy>::operator()() [with shared_obj_type = shared_obj_type, thread_pool_type = thread_pool_type, serverlet_type = void (*)(int, shared_obj_type), accept_fail_policy = utils::thread::default_accept_fail_policy]' /usr/include/boost/function/function_template.hpp:155: instantiated from `static void boost::detail::function::void_function_obj_invoker0<FunctionObj, R>::invoke(boost::detail::function::function_buffer&) [with FunctionObj = utils::thread::tcp_server<shared_obj_type, thread_pool_type, void (*)(int, shared_obj_type), utils::thread::default_accept_fail_policy>, R = void]' /usr/include/boost/function/function_template.hpp:368: instantiated from `void boost::detail::function::basic_vtable0<R, Allocator>::init(FunctionObj, boost::detail::function::function_obj_tag) [with FunctionObj = utils::thread::tcp_server<shared_obj_type, thread_pool_type, void (*)(int, shared_obj_type), utils::thread::default_accept_fail_policy>, R = void, Allocator = std::allocator<boost::function_base>]' /usr/include/boost/function/function_template.hpp:298: instantiated from `void boost::detail::function::basic_vtable0<R, Allocator>::init(F) [with F = utils::thread::tcp_server<shared_obj_type, thread_pool_type, void (*)(int, shared_obj_type), utils::thread::default_accept_fail_policy>, R = void, Allocator = std::allocator<boost::function_base>]' /usr/include/boost/function/function_template.hpp:277: instantiated from `boost::detail::function::basic_vtable0<R, Allocator>::basic_vtable0(F) [with F = utils::thread::tcp_server<shared_obj_type, thread_pool_type, void (*)(int, shared_obj_type), utils::thread::default_accept_fail_policy>, R = void, Allocator = std::allocator<boost::function_base>]' /usr/include/boost/function/function_template.hpp:655: instantiated from `void boost::function0<R, Allocator>::assign_to(Functor) [with Functor = utils::thread::tcp_server<shared_obj_type, thread_pool_type, void (*)(int, shared_obj_type), utils::thread::default_accept_fail_policy>, R = void, Allocator = std::allocator<boost::function_base>]' /usr/include/boost/function/function_template.hpp:513: instantiated from `boost::function0<R, Allocator>::function0(Functor, typename boost::enable_if_c< boost::type_traits::ice_not< boost::is_integral<Functor>::value>::value, int>::type) [with Functor = utils::thread::tcp_server<shared_obj_type, thread_pool_type, void (*)(int, shared_obj_type), utils::thread::default_accept_fail_policy>, R = void, Allocator = std::allocator<boost::function_base>]' tests/boost_tcp_server_test.cpp:24: instantiated from here /root/cpp-utils-header-lib/include/utils/thread/tcp_connection.hpp:61: error: functional cast expression list treated as compound expression /root/cpp-utils-header-lib/include/utils/thread/tcp_connection.hpp:61: warning: left-hand operand of comma has no effect /root/cpp-utils-header-lib/include/utils/thread/tcp_connection.hpp:61: error: cannot convert `((void)((utils::thread::tcp_connection<shared_obj_type, thread_pool_type, void (*)(int, shared_obj_type)>*)this)->utils::thread::tcp_connection<shared_obj_type, thread_pool_type, void (*)(int, shared_obj_type)>::newsockfd, ((utils::thread::tcp_connection<shared_obj_type, thread_pool_type, void (*)(int, shared_obj_type)>*)this)->utils::thread::tcp_connection<shared_obj_type, thread_pool_type, void (*)(int, shared_obj_type)>::obj)' from type `shared_obj_type' to type `void (*)(int, shared_obj_type)'

1 0

Update: application failed to initialize, bad jmp to malloc?
by David Daeschler 15 Aug '07

15 Aug '07

I'm sorry this post is so long, I'm looking for someone who may have experienced this, or knows enough about what I am rambling about to help me. I haven't been able to run our app built with MINGW for a week now, and It's starting to become a problem. This is a followup to a previous post entitled "Wrong DLL init routine being called?". I am starting a new post because it appears as if the stack traces I was getting before were wrong. I now have more information, and feel I am closer to solving this. When I try to load a test application I'm receiving the message: "The application failed to initialize properly (0xc0000005). Click on OK to terminate the application." I am not using auto-imports, so solutions referring to them have not helped me. I have always been winding up in malloc during the crashes I've been experiencing in calls to DLL initialization routines. I've been able to get a stack trace that lands up inside dllcrt1.c (the STATIC MINGW runtime) and shows me which call to malloc is segfaulting. The stack trace is as follows: #0 0x003e14a0 in malloc () #1 0x003e111c in DllMainCRTStartup@12 (hDll=0x3e0000, dwReason=1, lpReserved=0x22fd30) at dllcrt1.c:56 #2 0x7c9011a7 in ntdll!LdrSetAppCompatDllRedirectionCallback () from C:\WINDOWS\system32\ntdll.dll #3 0x003e0000 in ?? () #4 0x00000001 in ?? () #5 0x003e10c0 in __dll_exit () at dllcrt1.c:149 #6 0x00000000 in ?? () with frame 1 (inside dllcrt1.c) as: (gdb) f 1 #1 0x003e111c in DllMainCRTStartup@12 (hDll=0x3e0000, dwReason=1, lpReserved=0x22fd30) at dllcrt1.c:56 56 first_atexit = (p_atexit_fn*) malloc (32 * sizeof (p_atexit_fn)); Current language: auto; currently c (gdb) list 51 #endif 52 53 /* Initialize private atexit table for this dll. 54 32 is min size required by ANSI */ 55 56 first_atexit = (p_atexit_fn*) malloc (32 * sizeof (p_atexit_fn)); 57 if (first_atexit == NULL ) /* can't allocate memory */ 58 { 59 errno=ENOMEM; 60 return FALSE; Notice line 56. It seems innocent enough, how could a call to malloc be crashing? Well I called malloc from insidge gdb, and it worked fine, so I then dug further in and noticed that the malloc symbol that gdb is seeing is: (gdb) print malloc $1 = {<text variable, no debug info>} 0x40c780 <malloc> 0x40c780, okay, lets see a disassembly: Dump of assembler code for function malloc: 0x0040c780 <malloc+0>: jmp *0x41b1dc So there is a jump to 0x41b1dc, sure enough that lands us inside of: (gdb) disas 0x41b1dc Dump of assembler code for function _imp__malloc: 0x0041b1dc <_imp__malloc+0>: pop %es 0x0041b1dd <_imp__malloc+1>: les (bad),%eax 0x0041b1de <_imp__malloc+2>: ret $0x77 Ahh, import stub that leads us to: (gdb) disas _imp__malloc Dump of assembler code for function msvcrt!malloc: 0x77c2c407 <msvcrt!malloc+0>: mov %edi,%edi 0x77c2c409 <msvcrt!malloc+2>: push %ebp 0x77c2c40a <msvcrt!malloc+3>: mov %esp,%ebp 0x77c2c40c <msvcrt!malloc+5>: cmpl $0x0,0x77c62418 0x77c2c413 <msvcrt!malloc+12>: jne 0x77c2c420 <msvcrt!malloc+25> 0x77c2c415 <msvcrt!malloc+14>: call 0x77c1ef38 <msvcrt!__initenv+77> 0x77c2c41a <msvcrt!malloc+19>: test %eax,%eax 0x77c2c41c <msvcrt!malloc+21>: jne 0x77c2c420 <msvcrt!malloc+25> 0x77c2c41e <msvcrt!malloc+23>: pop %ebp 0x77c2c41f <msvcrt!malloc+24>: ret 0x77c2c420 <msvcrt!malloc+25>: pushl 0x77c61808 0x77c2c426 <msvcrt!malloc+31>: pushl 0x8(%ebp) 0x77c2c429 <msvcrt!malloc+34>: call 0x77c2c3d4 <msvcrt!free+441> 0x77c2c42e <msvcrt!malloc+39>: pop %ecx 0x77c2c42f <msvcrt!malloc+40>: pop %ecx 0x77c2c430 <msvcrt!malloc+41>: pop %ebp 0x77c2c431 <msvcrt!malloc+42>: ret 0x77c2c432 <msvcrt!malloc+43>: int3 0x77c2c433 <msvcrt!malloc+44>: int3 0x77c2c434 <msvcrt!malloc+45>: int3 0x77c2c435 <msvcrt!malloc+46>: int3 0x77c2c436 <msvcrt!malloc+47>: int3 End of assembler dump. Good, this is where I would expect to be, right at home inside of msvcrt. But now take a look at the first frame of our original stack trace. #0 0x003e14a0 in malloc () 0x3e14a0.. Umm, hmmm, wierd. Let's see where that leads us? (gdb) disas 0x3e14a0 Dump of assembler code for function malloc: 0x003e14a0 <malloc+0>: jmp *0x90c0609c I'd hate to say it, but there is no 0x90x0609c. That explains the segfault. Let's see what else is around 0x3e14a0... (gdb) disas 0x3e1490 Dump of assembler code for function _pei386_runtime_relocator: 0x003e1470 <_pei386_runtime_relocator+0>: mov $0x90c03034,%ecx 0x003e1475 <_pei386_runtime_relocator+5>: push %ebp 0x003e1476 <_pei386_runtime_relocator+6>: cmp $0x90c03034,%ecx 0x003e147c <_pei386_runtime_relocator+12>: mov %esp,%ebp 0x003e147e <_pei386_runtime_relocator+14>: jae 0x3e1498 <_pei386_runtime_relocator+40> 0x003e1480 <_pei386_runtime_relocator+16>: mov 0x4(%ecx),%edx 0x003e1483 <_pei386_runtime_relocator+19>: mov (%ecx),%eax 0x003e1485 <_pei386_runtime_relocator+21>: add $0x8,%ecx 0x003e1488 <_pei386_runtime_relocator+24>: add $0x90c00000,%edx 0x003e148e <_pei386_runtime_relocator+30>: add %eax,(%edx) 0x003e1490 <_pei386_runtime_relocator+32>: cmp $0x90c03034,%ecx 0x003e1496 <_pei386_runtime_relocator+38>: jb 0x3e1480 <_pei386_runtime_relocator+16> 0x003e1498 <_pei386_runtime_relocator+40>: pop %ebp 0x003e1499 <_pei386_runtime_relocator+41>: ret End of assembler dump. That looks like static libgcc to me. So is libgcc calling the wrong malloc for some reason? Why? Is this a relocation problem? Is there any way I can fix this? Is there anyone else I should be asking? I am using the dwarf2 GCC 4.2.1, but I had the same results with gcc 3.4.5 (though with less details on the crash) I was thinking that maybe shared libgcc would fix my problem, but I can't seem to link with it. When I specify -shared-libgcc it says I'm missing libgcc_s.a which I can't find anywhere. Details on my setup: $ gcc -v Using built-in specs. Target: mingw32 Configured with: ../gcc-4.2.1-2-src/configure --with-gcc --enable-libgomp --host=mingw32 --build=mingw32 --target=mingw32 --program-suffix=-dw2 --with-arch=i486 --with-tune=generic --disable-werror --prefix=/mingw --with-local-prefix=/mingw --enable-threads --disable-nls --enable-languages=c,c ++,fortran,objc,obj-c++,ada --disable-win32-registry --disable-sjlj-exceptions --enable-libstdcxx-debug --enable-cxx-flags=-fno-function-sections -fno-data-sections --enable-version-specific-runtime-libs --disable-bootstrap Thread model: win32 gcc version 4.2.1-dw2 (mingw32-2) $ld -v GNU ld version 2.17.50 20060824 MINGW runtime is a debug compiled version of mingw-runtime-3.13

1 1