This error means that you attempt to read out of bounds of a vector, or a string.
It's a bug in your solution, and not a kata issue.

What does your solution return for n=9876543210?

Can you help me to figure out what does this error means?

UndefinedBehaviorSanitizer:DEADLYSIGNAL
==1==ERROR: UndefinedBehaviorSanitizer: SEGV on unknown address 0x000000000000 (pc 0x00000042c030 bp 0x7ffd4839c200 sp 0x7ffd4839c1c0 T1)
==1==The signal is caused by a READ memory access.
==1==Hint: address points to the zero page.
==1==WARNING: invalid path to external symbolizer!
==1==WARNING: Failed to use and restart external symbolizer!
#0 0x42c02f (/workspace/test+0x42c02f)
#1 0x42581f (/workspace/test+0x42581f)
#2 0x429268 (/workspace/test+0x429268)
#3 0x4285a2 (/workspace/test+0x4285a2)
#4 0x426dbe (/workspace/test+0x426dbe)
#5 0x42662d (/workspace/test+0x42662d)
#6 0x42631b (/workspace/test+0x42631b)
#7 0x42bcd5 (/workspace/test+0x42bcd5)
#8 0x42595d (/workspace/test+0x42595d)
#9 0x7f4c5f37cbf6 (/lib/x86_64-linux-gnu/libc.so.6+0x21bf6)
#10 0x404799 (/workspace/test+0x404799)

UndefinedBehaviorSanitizer can not provide additional info.
==1==ABORTING

I am going to close this issue as a user error. If you are really, really sure your code is correct, plese post here:

• your code (formatted and marked as spoiler),
• input of failing tests,
• failure message, and/or value returned by your code and value expected by tests.

You can also come to #help-solve channel of Codewars Discord, someone will definitely help there.

Your solution seems to return invalid, too small values:

Testing for 4440220
   It should work for random inputs too: expected 4440022 to equal 4442002

expected 1234567089 to equal 1234567908 - my code produce correct: 1234567098

This does not seem to be the case. After adding logs to your solution, I can see:

Input:1234567890
Your result: 1234567089
   expected 1234567089 to equal 1234567908

Your code does not produce 1234567098.

Search table name in thos kata is a kind of fun.

I agree with your sort definintions.
Looks like no one cares about this requirement.
They will met terrible news someday - that SQL return any data in any order.