Re: profiling embedded lua

[Geoff Leyland <geoff_leyland@...>]

On 11/10/2011, at 10:09 PM, Oskar Forsslund wrote:

> This might have something to do with what my code is that I'm profiling
> 
> C:\Program Files (x86)\Lua\5.1>luatrace.profile
> 
> C:\Program Files (x86)\Lua\5.1>lua -e "require('luatrace.profile').go()"
> lua: .\luatrace\profile.lua:125: attempt to index local 'thread' (a nil value)
> stack traceback:
>         .\luatrace\profile.lua:125: in function 'call_on_thread'
>         .\luatrace\profile.lua:213: in function 'record'
>         .\luatrace\trace_file.lua:133: in function 'read'
>         .\luatrace\profile.lua:459: in function 'go'
>         (command line):1: in main chunk
>         [C]: ?
> C:\Program Files (x86)\Lua\5.1>
> 
> running luatrace.profile has not been an issue after I learned how to do it properly. With the output from my application however, this happened

Are you using coroutines?

Could you compress and send me your trace-out.txt? (off-list)