Errors when using crashdetect

Question

Errors when using crashdetect

oscar-broman opened this issue 10 years ago · comments

Everything appears to work as it should, but the server log gets spammed with this:

[21:42:43] [debug] Run time error 20: "Invalid index parameter (bad entry point)"
[21:42:43] [debug] Run time error 20: "Invalid index parameter (bad entry point)"
[21:42:44] [debug] Run time error 20: "Invalid index parameter (bad entry point)"
[21:42:44] [debug] Run time error 20: "Invalid index parameter (bad entry point)"
[21:42:44] [debug] Run time error 20: "Invalid index parameter (bad entry point)"
[21:42:45] [debug] Run time error 20: "Invalid index parameter (bad entry point)"
[21:42:46] [debug] Run time error 20: "Invalid index parameter (bad entry point)"
[21:42:46] [debug] Run time error 20: "Invalid index parameter (bad entry point)"
[21:42:47] [debug] Run time error 20: "Invalid index parameter (bad entry point)"
[21:42:48] [debug] Run time error 20: "Invalid index parameter (bad entry point)"
[21:42:48] [debug] Run time error 20: "Invalid index parameter (bad entry point)"

Gamer_Z · Answer 1 · Thu Jan 15 2015 13:00:44 GMT+0800 (China Standard Time)

I can't seem to reproduce this bug (I don't even have any information on this) and in the sampgdk source and in my source there are absolutely no signs of this text. It's a error caused from inside a PAWN script.

OR, this could be an issue with sampgdk (lacking main() in emulated amx?). (if this is the case, please contact @Zeex)

Please provide your server configuration and OS.

Zeex · Answer 2 · Thu Jan 15 2015 23:22:24 GMT+0800 (China Standard Time)

Update crashdetect to 4.15.1.