No, this is the only message: Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: 13 at address: 0x0000000000000000 0x00007fff8ca628a5 in misaligned_stack_error_entering_dyld_stub_binder ()
(gdb) bt #0 0x00007fff8ca628a5 in misaligned_stack_error_entering_dyld_stub_binder () #1 0x0000000000000061 in ?? () #2 0x0000000102c19218 in __func__.14673 () I also didn't do anything involving std::complex... On 5/13/14 4:54 PM, John Peterson wrote: > > > > On Tue, May 13, 2014 at 8:30 AM, Lorenzo Zanon > <[email protected] <mailto:[email protected]>> wrote: > > Hi, > > Besides, since I updated to version 0.9.3, I cannot use Exodus any > more. > The program crashes at the line e.g. > > ExodusII_IO(mesh).write_equation_systems ("out_3D.e", > equation_systems); > > Maybe I missed something in the configuration, although I didn't > change > anything w.r.t. last time. How can I solve this? > > > Hard to say what's happening without an error message. The Exodus > writer has pretty good error handling, so I'm a bit surprised you > didn't see something more informative... are you doing std::complex IO > by chance? > > -- > John ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
