[FLASH-USERS] Segfault while Initializing surr_blks

[Joel Long]

Klaus and Scott,

Okay, I will work on getting it compiled in debug and report back what I
find out. Yes, I have configured the makefile and verified that it is
pointing to all the right places, but thank you for checking.

Thanks,
Joel

On Tue, Feb 21, 2017 at 11:53 PM, Scott Feister <sfeister at gmail.com> wrote:

> Hi Joel,
>
> Glad to hear you're starting to use FLASH! I'll add to what Klaus said
> (and forgive me if this was obvious to you): After you installed versions
> of the various dependencies, did you add the paths to each of these
> libraries into a custom-tailored Makefile?
>
> I usually make a folder "[FLASHSOURCE]/sites/scottlaptop" and put a
> custom Makefile.h into that folder (in my case, I copy
> .../sites/Prototypes/Linux/Makefile.h and edit the first few lines
> pertaining to hypre, MPI, and hdf5). Then, I append the flag
> "-site=scottlaptop" to my setup flag.
>
> Scott
>
>
> Scott Feister, Ph.D.
> Postdoctoral Researcher, Flash Center for Computational Science
> University of Chicago, Department of Astronomy and Astrophysics
>
> On Tue, Feb 21, 2017 at 10:02 PM, Klaus Weide <klaus at flash.uchicago.edu>
> wrote:
>
>> On Tue, 21 Feb 2017, Joel Long wrote:
>>
>> > I am a new user just getting setup with FLASH. I am working on macOS
>> > 10.12.3. I have installed current versions of MPICH, Hypre, hdf5, etc.
>> >
>> > As a starting point, I am trying to run the Sedov explosion problem as
>> > described in the quick start section of the manual.
>> .....
>> > Program received signal SIGSEGV: Segmentation fault - invalid memory
>> > reference.
>> >
>> > Backtrace for this error:
>> > #0  0x1048ce579
>> > #1  0x1048cd945
>> > #2  0x7fffe09d4bb9
>> >
>> >
>> > Can anyone recommend what might be going wrong, or how I should
>> proceed? I
>> > can recompile with debugging symbols, but I'm doubting the root issue is
>> > actually a problem in the code, and if it were I wouldn't know how to
>> fix
>> > it anyway.
>>
>> Definitely try to compile with debugging, then run in gdb. This should at
>> least give you a better idea which part of the code is involved, and
>> possibly which library.
>>
>> Problems are often caused by incompatible libraries, especially if there
>> are several versions of a library present in the system.
>>
>> Klaus
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://flash.rochester.edu/pipermail/flash-users/attachments/20170222/fe922907/attachment.htm>