Please improve "failed to get schematic" errors

[verymilan]

Hi there, i host a little server for someone.
Somehow his server freezes after around 600MB place_schematic: failed to get schematic error messages.

So, this is a problem, we both have no idea what mod causes this trouble and i think the error message should at least print the schematic name which is called to make this easier.
Minetest is at commit eb49009.

kind Regards

[sofar]

the schematic isn't always a name. It could be a lua table, and that wouldn't have any identifiable information.

[Wuzzy2]

Well, then. Are there other ways to add more information to this error message? The intention of this issue is to make Minetest more debuggable, which is obviously needed.
So even some hints about where the schematic could come from would ease up debugging a lot.

Well, if the schematic does not have a name, then say it is a Lua table. If it has a name, print it.
If the schematic comes from a Lua table, say from which file it comes from. If I recall correctly, Lua is capable of introspection (with the debug table, but this may be a danger zone).

Besides, the error message itself is also pretty cryptic on its own. It is not clear what exactly is meant with “getting” a schematic, and why it “failed”. Did a file loading fail (then mention the attempted file name)? Had the schematic a bad syntax? Is the function called place_schematic or minetest.place_schematic? Was something nil / NULL? And so on.

[paramat]

This needs more information, the full error message or better a backtrace with using gdb maybe in debug mode. Otherwise we can't help. Closing in 1 month.

[rubenwardy]

paramat, this is a request for more debugging info not reporting a bug

[paramat]

Yes, misunderstood.

[paramat]

1+ year bump. Any core dev support?

[SmallJoker]

@paramat Yes. This output needs improvement.