The problem is that making calls to Lua form C++ seems to make profiling useless since I cant find any way of keeping the profiler healthy when transitioning from one language to the other
On Tue, Oct 4, 2011 at 12:55 PM, Patrick Rapin
<toupie300@gmail.com> wrote:
Is your purpose to profile Lua code inside your C++ application?
Profiling the C++ part with Visual Studio is quite easy.
To profile the Lua part, you will need to include an additional Lua library like luatrace [1]
[1] https://github.com/geoffleyland/luatrace
