This should fix it. Someone please check this and push it.
- Shawn On Wed, 15 Apr 2009, Bartosz Sawicki wrote:
I've realized similar problem with plotting function (Ubuntu i386). It seems that the new higher order mesh interface introduced by changeset 5962 is broken. Quick solution: $ hg update -r 5961 I try to localize the bug, and I think that the problem is in MeshGeometry copy constructor if _size_higher_order==0. See output gdb output for demo/pde/poisson/cpp/demo: Solving linear variational problem Applying boundary conditions to linear system. Solving linear system of size 1089 x 1089 (PETSc LU solver, umfpack). 0 terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Program received signal SIGABRT, Aborted. [Switching to Thread 0xb5b406c0 (LWP 12097)] 0xb7f83430 in __kernel_vsyscall () (gdb) where #0 0xb7f83430 in __kernel_vsyscall () #1 0xb64c08a0 in raise () from /lib/tls/i686/cmov/libc.so.6 #2 0xb64c2268 in abort () from /lib/tls/i686/cmov/libc.so.6 #3 0xb66fe778 in __gnu_cxx::__verbose_terminate_handler () from /usr/lib/libstdc++.so.6 #4 0xb66fc655 in ?? () from /usr/lib/libstdc++.so.6 #5 0xb66fc692 in std::terminate () from /usr/lib/libstdc++.so.6 #6 0xb66fc7ca in __cxa_throw () from /usr/lib/libstdc++.so.6 #7 0xb66fce23 in operator new () from /usr/lib/libstdc++.so.6 #8 0xb66fcf0d in operator new[] () from /usr/lib/libstdc++.so.6 #9 0xb7e8eec5 in dolfin::MeshGeometry::operator= (this=0xbfd8257c, geomet...@0xbfd82678) at dolfin/mesh/MeshGeometry.cpp:52 #10 0xb7e9566f in dolfin::Mesh::operator= (this=0xbfd82568, me...@0xbfd82664) at dolfin/mesh/Mesh.cpp:80 #11 0xb7f01a6f in FunctionPlotData (this=0xbfd82560, v...@0xbfd8283c) at dolfin/plot/FunctionPlotData.cpp:21 #12 0xb7efdc65 in dolfin::plot (v...@0xbfd8283c, mode= {static npos = 4294967295, _M_dataplus = {<std::allocator<char>> = {<__gnu_cxx::new_allocator<char>> = {<No data fields>}, <No data fields>}, _M_p = 0xbfd828d0 "$\b"}}) at dolfin/plot/plot.cpp:42 #13 0x0805ce54 in main () at main.cpp:67 cheers BArtosz Nuno David Lopes wrote:Ok. systems Ubuntu 8.10 64b Ubuntu8.10 32b in different machines. I've updated DOLFIN today It was working until the update. The operator "<<" crashes the systems when writting to a xml format. It doesn't create the file. With other file formats no problems Viper is working fine) The demos don't work (poisson, cpp, for instance). Is it just me? BTW: Is there a way of running viper in the background , (with the dolfin::plot function), and replot the updated data automatically. Instead of waiting for a "q" key press and hanging the dolfin process . For time-dependent problems? On Wednesday 15 April 2009 15:41:36 Ola Skavhaug wrote:On Wed, Apr 15, 2009 at 4:28 PM, Nuno David Lopes <[email protected]>wrote:Hi! Is the plotting system, (with xml file) working? ------------- (xml) file << function ------------- crashes my systems... Is it supposed to? thanks!I'm not able to process this bug report. A lot of details are missing :) Could you fill in the missing pieces, like versions, operating system, concrete code example etc. Thanks, Ola-- Nuno David Lopes e-mail:[email protected] (FCUL/CMAF) [email protected] (ISEL) http://ptmat.ptmat.fc.ul.pt/%7Endl/ Wed Apr 15 14:56:08 WEST 2009 _______________________________________________ DOLFIN-dev mailing list [email protected] http://www.fenics.org/mailman/listinfo/dolfin-dev------------------------------------------------------------------------ _______________________________________________ DOLFIN-dev mailing list [email protected] http://www.fenics.org/mailman/listinfo/dolfin-dev_______________________________________________ DOLFIN-dev mailing list [email protected] http://www.fenics.org/mailman/listinfo/dolfin-dev
dolfin-walker-2009-04-15.hg
Description: Binary data
_______________________________________________ DOLFIN-dev mailing list [email protected] http://www.fenics.org/mailman/listinfo/dolfin-dev
