Closed jeffdaily closed 6 years ago
What compiler and branch?
g++ (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
On branch develop Your branch is up-to-date with 'origin/develop'.
Definitely something we need to fix, but probably not something easy. I have seen a few things in linux that depend on which thread was terminated first, which is challenging to deal with.
In the meantime try adding
cleanupHelicsLibrary (); after the fed-finalize() call see if that removes the seg fault.
I am going to try a few things and might see if can replicate the issue.
which boost version did you use? How many cores on your system?
Do you just run two of those and the broker?
@jeffdaily can you check this again with the latest develop branch after the merge of #144
@jeffdaily have you checked this recently or can we close the issue
On ubuntu 16 VM. Using latest develop head. Built and installed debug static build of helics. Built and installed latest ns-3 examples. Attempted to run two instances of
./ns-3-dev-git/build/contrib/helics/examples/ns3-dev-fed-sndrcv-debug
, each with a unique federate name. (Examples are simple and do not take command-line params, so I set the federate name to argv[1] if it exists.) By default the examples provide full level 4 debugging. Their code is here.First, ran the broker simply
../HELICS-build-Debug-install/bin/helics_broker 2 --loglevel=4
.Ran the two federates. Both federates segfault after seeing
7221-5a2bb694-6247-4ffc-a1d2-27d17aeddd82::|| cmd:disconnect from 65537
.I ran one of the federates with gdb to get the stack trace: