|
[Sponsors] |
December 30, 2018, 10:35 |
SetFields SigSegV bug.
|
#1 |
New Member
Florian
Join Date: Dec 2018
Posts: 20
Rep Power: 8 |
Hello there,
I'm having some issues with OpenFOAM 2.3.0's setFields command. I've ran the check mesh several times and corrected the faults it gave me and then moved to setFields in preparation of running the actual simulation. Now the program just delivers me this: Build : 2.3.0-f5222ca19ce6 Exec : setFields sigFpe : Enabling floating point exception trapping (FOAM_SIGFPE). fileModificationChecking : Monitoring run-time modified files using timeStampMaster allowSystemOperations : Disallowing user-supplied system call operations ? ? ? ? #0 Foam::error:rintStack(Foam::Ostream&) at ??:? #1 Foam::sigSegv::sigHandler(int) at ??:? #2 in "/lib/x86_64-linux-gnu/libc.so.6" #3 in "/home/rieth/OpenFOAM/OpenFOAM-2.3.0/platforms/linux64GccDPOpt/bin/setFields" #4 in "/home/rieth/OpenFOAM/OpenFOAM-2.3.0/platforms/linux64GccDPOpt/bin/setFields" #5 in "/home/rieth/OpenFOAM/OpenFOAM-2.3.0/platforms/linux64GccDPOpt/bin/setFields" #6 __libc_start_main in "/lib/x86_64-linux-gnu/libc.so.6" #7 in "/home/rieth/OpenFOAM/OpenFOAM-2.3.0/platforms/linux64GccDPOpt/bin/setFields" Segmentation fault (core dumped) After googling around for a bit i found out that this is a segmentation error where the program tries to access data it can't or did i misunderstand that? Sadly i found nothing on how to actually fix the issue. If anyone could offer me some assistance on how to get this to run i'd be very grateful. Also anyone reading this around new years i hope you get into the new year well. Greetings Florian |
|
December 30, 2018, 17:11 |
|
#2 |
Retired Super Moderator
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,981
Blog Entries: 45
Rep Power: 128 |
Quick answer: It's possible that you've tripped over a bug that was fixed later on in OpenFOAM 2.3.1 and/or 2.3.x and/or 2.4.x.
You can have 2.4.x or 2.4.0 installed in parallel with the 2.3.0 version, then run setFields only with that version, so that you can workaround this specific bug. More details on how to have more than one version installed, are provided here: https://openfoamwiki.net/index.php/I...nFOAM_versions
__________________
|
|
December 31, 2018, 09:45 |
|
#3 |
New Member
Florian
Join Date: Dec 2018
Posts: 20
Rep Power: 8 |
I'll give that a try later today or tomorrow and report back!
Thx in advance! |
|
January 4, 2019, 07:09 |
|
#4 |
New Member
Florian
Join Date: Dec 2018
Posts: 20
Rep Power: 8 |
Alright i tried installing OpenFOAM 2.3.1 but when i get to setFields it still gives me the segmentation error. Could it have something to do with the Mesh? Even though CheckMesh returns that the mesh is ok...
I'll try 2.4 now see if that helps. |
|
January 4, 2019, 19:23 |
|
#5 |
Retired Super Moderator
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,981
Blog Entries: 45
Rep Power: 128 |
Quick answer: The only other thing that comes to mind is that something very wrong might be defined in the "setFieldsDict" file... can you share that file with us?
|
|
Tags |
sigsegv |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
mapFields major bug | alchem | OpenFOAM Bugs | 14 | September 15, 2023 13:48 |
Manual decomposition using setFields | RL-S | OpenFOAM Pre-Processing | 8 | July 3, 2023 09:51 |
error: Received signal SIGSEGV | ianziti92 | Fluent UDF and Scheme Programming | 2 | December 5, 2018 17:25 |
Bug in Workbench CFX | Pierre1 | CFX | 6 | August 2, 2017 01:18 |
Problems with the execution of the setFields utility. | foamer | OpenFOAM Pre-Processing | 5 | June 3, 2013 13:24 |