What could be the reason for 'Error 3050008: Abort Called'

Question

I'm getting the following error without any further description. What could be the issue for that?

I'm performing some binary arithmetics when calling this action, are there any known problems with that?

Error 3050008: Abort Called
Error Details:
abort() called
pending console output:

contract compiled with eosio.cdt, deployed on kylin, using eoscanada-endpoint.

UPDATE

Figured it out, reason was accessing a vector at missing index.

You should add the bit of code that caused this problem, and then right out your answer. This helps other people and it also improves search engine results for similar problems — Phillip Hamnett - EOS42, Commented Jul 4, 2019 at 8:28
it would be useful if the error indicated the line at which the error is being generated. otherwise having to find the error in a long codebase is pretty painful — ekkis, Commented Nov 3, 2019 at 20:30

Phillip Hamnett - EOS42 · Accepted Answer · 2020-01-13 15:20:32Z

5

Abort Called is usually an indicating of a segmentation violation. So look for things like:

answered Jan 13, 2020 at 15:20

4,7441 gold badge14 silver badges57 bronze badges

1

For me it was a cast of an empty string to uint that caused that error.
– Eulinky
Commented Apr 16, 2021 at 13:54

Add a comment |

1 Answer 1