Ok... So.... Through some combination of make clean and make the
problem appears to be fixed... And I'm having trouble reproducing it.

Strange... If I can figure out what I did to make that happen again, I
will be sure to get the traceback. Sorry about that.

Andrea

On Mon, Mar 8, 2010 at 2:56 PM, Roy Stogner <[email protected]> wrote:
>
> On Mon, 8 Mar 2010, Andrea Hawkins wrote:
>
>> I'm attempting to do mesh refinement with the
>> PatchRecoveryErrorEstimator (both coarsening and refining). This works
>> quite well, and if I do a restart with the adapted mesh just asking it
>> to continue with refining it works fine. However, if I ask it to
>> continue both refining and coarsening I get the following error when
>> it attempts to refine:
>
>> [11]PETSC ERROR: Caught signal number 7 BUS: Bus Error, possibly
>> illegal memory access
>
>> Has anyone ever seen this before?
>
> Vikram ran into some as-yet-unidentified problem with the new L2
> option for PatchRecovery last week, but that's almost certainly
> unrelated.
>
> There's a bug in our libHilbert interface that could have corrupted an
> old output file; that's why for now we disable libHilbert by default.
> Assuming you're trying to restart from newly generated output files,
> would you make sure LIBMESH_HAVE_LIBHILBERT is commented out in
> libmesh_config.h, please?
>
> Is this the first error you hit in dbg mode?  If not then knowing what
> assert first fails might help.  If so, then could you run though
> -start_in_debugger and give us a stack trace?
>
> Thanks,
> ---
> Roy
>

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Libmesh-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users

Reply via email to