ExBemined Posted July 28, 2015 Share Posted July 28, 2015 Annoyed with not being able to see from where in script my external function was being called, I did a small experiment. Added one function to Machine class with only two lines of code within, this allowed script callstack to be requested on demand from the Visual Studio debugger :D void Machine::debugDump() const { Log::message("Stack dump:\n%s",interpreter->getStackDump().get()); Log::message("Call stack:\n%s",interpreter->getCallStack().get()); } It's very easy to use, just navigate to Machine::run in the callstack, and in the immediate window enter debugDump() and it will output the callstack of script functions that were leading to the external function being called. Perhaps something that can be included by default? 1 Link to comment
silent Posted July 29, 2015 Share Posted July 29, 2015 Indeed, it can be very handy in some cases. I've added this suggestio to our internal TODO list (is not yet reviewed by the dev team). Thank you! How to submit a good bug report --- FTP server for test scenes and user uploads: ftp://files.unigine.com user: upload password: 6xYkd6vLYWjpW6SN Link to comment
Recommended Posts