[CIG-SHORT] ALE::Exception

[Brad Aagaard]

Rowena-

ALE::Exception means that Sieve (the finite-element storage stuff) found an 
error. You can try running PyLith inside gdb (-start_in_debugger command line 
argument). Enter "continue" at the gdb prompt. Hopefully it will fail inside 
gdb so you can type "backtrace" and get a stack trace. If you can send a 
stacktrace, that should help identify the problem. Alternatively, send me a 
tarball with the input files. Also, let me know if you are running on 
multiple processors.

Brad


On Monday 23 October 2006 5:16 pm, Rowena Lohman wrote:
> I just asked Eric Hetland about this, since he ran into a similar problem
> back in August, but I didn't see any response to his question in the CIG
> list archive.
>
> I'm getting the following error when I run Pylith using my own,
> script-generated input files:
>
> terminate called after throwing an instance of 'ALE::Exception'
> /u/vento0/rlohman/pylith-0.8.1-linux-x86/bin/mpirun.ch_shmem: line 91:
> 11789 Aborted
>
> Question:  Is this type of error likely to be a formatting issue (very
> possible since I'm writing the  input files in matlab), or is it a more
> difficult issue involving  a poorly-structured mesh?
>
> I'm not too familiar with ALE but am reading through the scanner.cc file in
> hopes of figuring out what's wrong.
>
> Thanks!
> Ro