clang & clang++
Apple LLVM version 4.2 (clang-425.0.28) (based on LLVM 3.2svn)
Target: x86_64-apple-darwin12.4.0
Thread model: posix
Just to clarify, I have been using it successfully for almost a year. So, I am
a little puzzled by this error.
It happens with the call to localtime in timestamp.C, particularly when the
destructor to perflog is called. I compile the code
// Call C-style time getting functions
time_t now = time(NULL);
tm* tm_struct = localtime(&now);
I have compiled my library with the following options:
PETSC_DIR=/Users/manav/Documents/codes/numerical_lib/petsc/real
SLEPC_DIR=/Users/manav/Documents/codes/numerical_lib/slepc/real
FC=gfortran-mp-4.8 F77=gfortran-mp-4.8 CC=clang CXX=clang++
CXXFLAGS="-I/opt/local/include/openmpi -I/opt/local/include/metis
-I/opt/local/include/vtk-5.10" CFLAGS="-I/opt/local/include/openmpi
-I/opt/local/include/metis" LIBS="-L/opt/local/lib -lmpi_cxx -lmpi" ./configure
--prefix=${PWD}/../ --enable-mpi --enable-dependency-tracking --enable-fortran
--enable-shared --enable-exceptions --disable-openmp
--disable-default-comm-world --enable-tracefiles --enable-amr
--enable-vsmoother --enable-periodic --enable-dirichlet --enable-parmesh
--enable-nodeconstraint --enable-ghosted --enable-pfem --enable-ifem
--enable-second --enable-xdr --enable-reference-counting --enable-perflog
--enable-examples --enable-boost --disable-trilinos --enable-tbb --enable-sfc
--enable-tecplot --enable-metis --enable-parmetis --enable-tetgen
--enable-triangle --enable-vtk --
enable-hdf5 --enable-libHilbert --enable-nanoflann --enable-exodus
--enable-netcdf --enable-petsc --enable-slepc --with-mpi=/opt/local
--with-trilinos=/usr/local/trilinos --with-tbb=/opt/local/tbb41_20121003oss
--with-metis=internal --with-hdf5=/opt/local
--with-vtk-lib=/opt/local/lib/vtk-5.10
--with-vtk-include=/opt/local/include/vtk-5.10 --with-methods="opt dbg"
I was able to reproduce it by downloading the library, compiling with these
options, followed by make, then make check. The first example ended with a
similar error.
The examples run without problems with perflog disabled.
Manav
On Aug 4, 2013, at 10:31 PM, John Peterson <[email protected]> wrote:
> What compiler?
>
> --
> John
>
> On Aug 4, 2013, at 10:19 AM, Manav Bhatia <[email protected]> wrote:
>
>> Hi,
>>
>> I am using libMesh on a Mac with 10.8.4. I updated to the latest git
>> repository and am getting the following error upon running introduction_ex1.
>> I have never seen this before.
>>
>> Has anyone else run into this same issue on Mac or otherwise? Could any
>> recent changes have made this impact?
>>
>> Thanks,
>> Manav
>>
>>
>> Program received signal EXC_BAD_ACCESS, Could not access memory.
>> Reason: KERN_INVALID_ADDRESS at address: 0x0000000105af5db8
>> 0x00000001047ecfcd in __findenv ()
>> (gdb) where
>> #0 0x00000001047ecfcd in __findenv ()
>> #1 0x00000001047ed020 in getenv ()
>> #2 0x00000001047d27dd in _st_tzset_basic ()
>> #3 0x00000001047d4044 in localtime ()
>> #4 0x0000000100d2eea9 in libMesh::Utility::get_timestamp () at
>> src/utils/timestamp.C:46
>> #5 0x0000000100cd939c in libMesh::PerfLog::get_info_header
>> (this=0x101bbe818) at src/utils/perf_log.C:102
>> #6 0x0000000100cdd4db in libMesh::PerfLog::get_log (this=0x101bbe818) at
>> src/utils/perf_log.C:571
>> #7 0x0000000100cd9282 in libMesh::PerfLog::print_log (this=0x101bbe818) at
>> src/utils/perf_log.C:588
>> #8 0x0000000100cd9187 in libMesh::PerfLog::~PerfLog (this=0x101bbe818) at
>> src/utils/perf_log.C:62
>> #9 0x0000000100cd9155 in libMesh::PerfLog::~PerfLog (this=0x101bbe818) at
>> src/utils/perf_log.C:60
>> #10 0x00000001047eb307 in __cxa_finalize ()
>> #11 0x00000001047ecf57 in exit ()
>> #12 0x00000001047557e8 in start ()
>> (gdb)
>> ------------------------------------------------------------------------------
>> Get your SQL database under version control now!
>> Version control is standard for application code, but databases havent
>> caught up. So what steps can you take to put your SQL databases under
>> version control? Why should you start doing it? Read more to find out.
>> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Libmesh-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/libmesh-users
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
Libmesh-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users
