here is the backtrace:
Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_INVALID_ADDRESS at address: 0x06a0afe1 0xa0b02584 in std::wclog () (gdb) bt #0 0xa0b02584 in std::wclog () #1 0xa0b025f0 in std::wclog () #2 0x00009db7 in global constructors keyed to cl_module__cl_prin_globals__firstglobalfun () at ./base/output/ cl_prin_globals.cc:33 #3 0x00009c9a in __static_initialization_and_destruction_0 (__initialize_p=1, __priority=65535) at ../include/cln/io.h:91 #4 0x00009db7 in global constructors keyed to cl_module__cl_prin_globals__firstglobalfun () at ./base/output/ cl_prin_globals.cc:33 #5 0x000026f4 in __static_initialization_and_destruction_0 (__initialize_p=2, __priority=65535) at ../include/cln/io.h:91 #6 0x0000275d in global constructors keyed to _Z15test_elementaryv () at exam.cc:51 #7 0x8fe10168 in __dyld__ZN16ImageLoaderMachO16doInitializationERKN11ImageLoader11LinkCon textE () #8 0x8fe0a516 in __dyld__ZN11ImageLoader23recursiveInitializationERKNS_11LinkContextE () #9 0x8fe0ca08 in __dyld__ZN11ImageLoader15runInitializersERKNS_11LinkContextE () #10 0x8fe031b4 in __dyld__ZN4dyld24initializeMainExecutableEv () #11 0x0000264d in _call_mod_init_funcs () at /SourceCache/Csu/Csu-58/ crt.c:304 #12 0x00002579 in _start (argc=1, argv=0xbffff86c, envp=0xbffff874) at /SourceCache/Csu/Csu-58/crt.c:222 #13 0x00002529 in start ()
Well, I've a (almost trivial) patch that makes it work fine on Intel Macs, according to the submitter of the bug. For the next release, I intend to fix it in a very conservative way. For this purpose, I need to know how to identify an Intel Mac using preprocessor macros. Does anyone on this list know which macro is set there? (Hint: on a Linux system, that would be "__linux__".) (I've already tried contacting people, finding it in the gcc sources, googling, but was unable to find anything.) Regards -richy. -- Richard B. Kreckel <http://www.ginac.de/~kreckel/>