v1.6.1 segfault with abi generation

[johndebord]

v1.6.1 of eosio-cpp currently has a bug which causes a seg fault, but only with abi generation and under certain circumstances.

[cryptosig]

I believe I'm running into this error as well
Update:
I have traced the segmentation fault whilst generating abi to the following line of code, "fixed_bytes<32> bytes_value;", declaring this inside of my table is what has been causing my seg fault. I hope this helps.

[johndebord]

@cryptosig This issue has been resolved. The problem we encountered was that the tool eosio-abigen segfaults when declaring a std::vector of itself within its own data structure.

---

For example:

#include <vector>

#include <eosio/contract.hpp>
#include <eosio/multi_index.hpp>

using namespace eosio;

struct [[eosio::contract]] main : eosio::contract {
   using contract::contract;

   struct [[eosio::table]] structure {
      std::vector<structure> vec;
   };

   [[eosio::action]] void act()
   { }
};

Compiles, but segaults during .abi generation.

---

#include <vector>

#include <eosio/contract.hpp>
#include <eosio/multi_index.hpp>

using namespace eosio;

struct [[eosio::contract]] con : eosio::contract {
   using contract::contract;

   struct [[eosio::table]] structure {
      std::vector<int> vec;
   };

   [[eosio::action]] void act()
   { }
};

Compiles and does not segault during .abi generation.

---

@cryptosig If the issue you're having is still not solved by this solution, please open up a new issue and provide some code/context of the issue you're encountering.

[znebby]

@johndebord How is this issue solved? 1.6.2 still SegFaults when a table references itself in a vector. Can we re-open this issue?

[jeffreyssmith2nd]

@znebby See issue #527, there's an ongoing discussion on that issue about table references in a vector.