Re: [Libmesh-users] remote_elem singleton setup

2015-03-12 Thread Paul T. Bauman
On Thu, Mar 12, 2015 at 12:01 PM, Manav Bhatia wrote: > > My next step is to get this to build on another machine which has a native > gcc4.1 compiler. I will see how that goes. (Fingers crossed). Man. And here I was thinking that GCC 4.4 was the oldest thing we had to worry about (in the GCC f

Re: [Libmesh-users] remote_elem singleton setup

2015-03-12 Thread Manav Bhatia
> On Mar 12, 2015, at 11:06 AM, Kirk, Benjamin (JSC-EG311) > wrote: > > >> On Mar 12, 2015, at 11:01 AM, Manav Bhatia wrote: >> >> My next step is to get this to build on another machine which has a native >> gcc4.1 compiler. I will see how that goes. (Fingers crossed). > > FWIW, I run a

Re: [Libmesh-users] remote_elem singleton setup

2015-03-12 Thread Kirk, Benjamin (JSC-EG311)
> On Mar 12, 2015, at 11:01 AM, Manav Bhatia wrote: > > My next step is to get this to build on another machine which has a native > gcc4.1 compiler. I will see how that goes. (Fingers crossed). FWIW, I run a build compatibility test with libMesh vanilla code (no dependencies) using gcc-3.4,

Re: [Libmesh-users] remote_elem singleton setup

2015-03-12 Thread Manav Bhatia
> On Mar 12, 2015, at 10:57 AM, John Peterson wrote: > > > > On Thu, Mar 12, 2015 at 9:48 AM, Manav Bhatia > wrote: > Got it to work. > > Changed the compiler to gcc-4.4 and things seems to be working fine. > > Good to know, but GCC 4.4 isn't much newer than In

Re: [Libmesh-users] remote_elem singleton setup

2015-03-12 Thread John Peterson
On Thu, Mar 12, 2015 at 9:48 AM, Manav Bhatia wrote: > Got it to work. > > Changed the compiler to gcc-4.4 and things seems to be working fine. > Good to know, but GCC 4.4 isn't much newer than Intel 11... I'd try to update to something newer as soon as possible unless you don't administer this

Re: [Libmesh-users] remote_elem singleton setup

2015-03-12 Thread Manav Bhatia
Got it to work. Changed the compiler to gcc-4.4 and things seems to be working fine. There may have been other things wrong with my earlier attempts: for example, I was using an intel-11.1 compiler to compile on an AMD Opteron machine. In any case, I can now more forward with some runs. Th

Re: [Libmesh-users] remote_elem singleton setup

2015-03-12 Thread Manav Bhatia
I have compared this with how the code executes on my Mac (which works fine). So far, my understanding is that RemoteElemSetup needs to be called prior to getting into this setup routine. But for some reason it is not in this case. Would that be a compiler error? Can this be forced in the code

Re: [Libmesh-users] remote_elem singleton setup

2015-03-12 Thread Roy Stogner
On Wed, 11 Mar 2015, Manav Bhatia wrote: I am working on getting the stack trace. The problem is that if I comment the “lock” line out, then the code crashes with a segmentation-fault without a stack trace. There is, obviously, something that I am not doing right. No need to comment the lock

Re: [Libmesh-users] remote_elem singleton setup

2015-03-12 Thread Roy Stogner
On Wed, 11 Mar 2015, Manav Bhatia wrote: > I have compared this with how the code executes on my Mac (which works fine). > So far, my understanding is that RemoteElemSetup needs to be called > prior to getting into this setup routine. But for some reason it is > not in this case. Would that be

Re: [Libmesh-users] remote_elem singleton setup

2015-03-11 Thread Manav Bhatia
> On Mar 11, 2015, at 11:43 AM, Roy Stogner wrote: > > > On Wed, 11 Mar 2015, Manav Bhatia wrote: > >> I double checked, and I am using a C++ compiler to link. > >> Moreover, I ran make check in the examples director, and came across the >> same problem. > > If you want to drop the issue

Re: [Libmesh-users] remote_elem singleton setup

2015-03-11 Thread Roy Stogner
On Wed, 11 Mar 2015, Manav Bhatia wrote: I double checked, and I am using a C++ compiler to link.  Moreover, I ran make check in the examples director, and came across the same problem.  If you want to drop the issue now that you've got a workaround, nobody will blame you. If you're curi

Re: [Libmesh-users] remote_elem singleton setup

2015-03-11 Thread Manav Bhatia
I double checked, and I am using a C++ compiler to link. Moreover, I ran make check in the examples director, and came across the same problem. -Manav > On Mar 11, 2015, at 11:35 AM, John Peterson wrote: > > > > On Wed, Mar 11, 2015 at 10:10 AM, Roy Stogner

Re: [Libmesh-users] remote_elem singleton setup

2015-03-11 Thread John Peterson
On Wed, Mar 11, 2015 at 10:10 AM, Roy Stogner wrote: > > On Wed, 11 Mar 2015, Manav Bhatia wrote: > > > It is not getting called. I put a breakpoint there (actually, in the > > constructor of Singleton::Setup::Setup()) and the code does not get > > to it. > > This is looking more and more like a

Re: [Libmesh-users] remote_elem singleton setup

2015-03-11 Thread Roy Stogner
On Wed, 11 Mar 2015, Manav Bhatia wrote: > It is not getting called. I put a breakpoint there (actually, in the > constructor of Singleton::Setup::Setup()) and the code does not get > to it. This is looking more and more like a compiler bug, then. You must be linking in remote_elem.C or you'd b

Re: [Libmesh-users] remote_elem singleton setup

2015-03-11 Thread Manav Bhatia
I added the line RemoteElem::create(); in between the calls to Singleton::setup() and libmesh_assert(remote_elem); Now the code is crashing in libMesh::ReferenceCounter::increment_constructor_count(). It seems like there may be another static initialization that reference counter depends

Re: [Libmesh-users] remote_elem singleton setup

2015-03-11 Thread Manav Bhatia
> On Mar 11, 2015, at 10:52 AM, Roy Stogner wrote: > > > On Wed, 11 Mar 2015, Manav Bhatia wrote: > >> I have compared this with how the code executes on my Mac (which works fine). > >> So far, my understanding is that RemoteElemSetup needs to be called >> prior to getting into this setup ro

Re: [Libmesh-users] remote_elem singleton setup

2015-03-11 Thread Manav Bhatia
Ok. So I am in the debugger and stepping through the code. The size of setup_cache in Singleton::setup() (line 84 of libMesh_singleton.C) is zero. So, the for loop is not doing anything. -Manav > On Mar 11, 2015, at 10:12 AM, Roy Stogner wrote: > > > On Wed, 11 Mar 2015, Manav Bhatia wrot

Re: [Libmesh-users] remote_elem singleton setup

2015-03-11 Thread Manav Bhatia
> On Mar 11, 2015, at 8:11 AM, Roy Stogner wrote: > > > On Wed, 11 Mar 2015, Manav Bhatia wrote: > >> I seem to be facing the same issue as described here: >> http://sourceforge.net/p/libmesh/mailman/message/31297017/ >> >> >> I

Re: [Libmesh-users] remote_elem singleton setup

2015-03-11 Thread Roy Stogner
On Wed, 11 Mar 2015, Manav Bhatia wrote: > I seem to be facing the same issue as described here: > http://sourceforge.net/p/libmesh/mailman/message/31297017/ > > > If I build with pthreads and tbb, the code hangs at the singleton:

[Libmesh-users] remote_elem singleton setup

2015-03-10 Thread Manav Bhatia
Hi, I seem to be facing the same issue as described here: http://sourceforge.net/p/libmesh/mailman/message/31297017/ If I build with pthreads and tbb, the code hangs at the singleton::setup call. Without pthreads, it seems