Virtual Stigmergy conflict resolver segfault

Question

Virtual Stigmergy conflict resolver segfault

Closed this issue 6 years ago · 3 comments

The conflict resolver of Virtual Stigmergy(VS) seems to crash with a Segmentation Fault.
It used to work with the older version of Buzz + Argos.
The latest version of Buzz + ARGOS causes a segmentation fault when a conflict resolver lambda function is called, in the result of a conflict. There is also an invalid free during the initialization part. I am attaching a minimalistic buzz script that leads to a Memory leak and the leak summary from Valgrind.
VS_Bug.txt
leak_summery.txt

Answer 1 · 2018-02-22T04:00:34.000Z

Thank you Carlo for the fix.

Answer 2 · 2018-02-23T22:09:01.000Z

I got the same segmentation fault problem when trying to run the same code on Khepera robots. I think the problem comes this time from BuzzKH4... What do you think?

Answer 3 · 2018-02-23T22:20:22.000Z

If you got the same problem, probably it's because you didn't update the Buzz VM on the khepera. Otherwise, there's a bug in the BuzzKH4 code, and it should be reported there.