Re: [Libmesh-devel] [Libmesh-users] Has anyone tripped this error?

[Derek G. <fri...@gm...>]

Ok - we just looked into this - Ben: It looks like you're not ever creating
RemoteElem which is why it's not getting registered.

At the bottom of remote_elem.h you have this:

extern const RemoteElem* remote_elem;

But that's just creating a pointer.  In the .C you have this:

const RemoteElem* remote_elem;

But, again, that's not creating a RemoteElem.

In fact, nothing is ever creating a RemoteElem... so it doesn't get
registered with the Singleton class.  In remote_elem.C you could do this:

extern const RemoteElem* remote_elem = new RemoteElem;

And that would fix it.

Derek



On Wed, Apr 3, 2013 at 5:32 AM, Kirk, Benjamin (JSC-EG311) <
ben...@na...> wrote:

> On Apr 3, 2013, at 1:41 AM, "Roy Stogner" <roy...@ic...>
> wrote:
>
> >
> >
> > On Tue, 2 Apr 2013, Cody Permann wrote:
> >
> >>> Weird - *all* my compilers on linux worked fine - gcc 4.4, 4.5, 4.6,
> 4.7, icc 12.0, 12.1,
> >>> 13.0, pgi's, open solaris…
> >>
> >> Alright, I'll give it a shot, I can't repeat the bad behavior on our
> Macs, even with the
> >> identical 4.7.2 compiler so it is a complicated problem indeed.
> >
> > We're now seeing remote_elem based failures on buildbot too; I'll see
> > if I can reproduce it elsewhere.
>
> Thanks. Ill prepare a pull request when I get in that undoes they change,
> but hopefully we can find a way to make it work!
>
> -Ben
>
>
> ------------------------------------------------------------------------------
> Minimize network downtime and maximize team effectiveness.
> Reduce network management and security costs.Learn how to hire
> the most talented Cisco Certified professionals. Visit the
> Employer Resources Portal
> http://www.cisco.com/web/learning/employer_resources/index.html
> _______________________________________________
> Libmesh-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libmesh-devel
>