Report calling native hash when failing

[AvarianKnight]

Segment

n/a

Importancy

Unclear or unintuitive

Improvement request

Currently calling a native with too large of a value (such as SetPedComponentVariation(ped, 12, 1, 0, 0) where 12 isn't a valid component id) will error with arg[1]: value too large, but this doesn't report the native used which can make it hard to debug what the error is.

Normal native execution fails would include the native hash of the native that was called to cause the error

fivem/code/components/citizen-scripting-lua/src/LuaScriptNatives.cpp

Lines 474 to 476 in 49406c4

	fx::ScriptTrace("%s: execution failed: %s\n", __func__, e.what());
	context.SetError("Execution of native %016llx in script host failed: %s", hash, e.what());

Area(s)

FiveM, Natives

Additional information

No response

[d22tny]

It normally has a stack trace attached but sometimes it doesn't show the stack trace. I opened a similar issue the first day the change was merged, and they've agreed that it would be okay to have the native hash included.

[AvarianKnight]

Haven't had a case of no stack trace being opened, just one that's very uninformative

See:

The line this point to is not useful at all