Re: profiling embedded lua

[Oskar Forsslund <matrixsmurfen@...>]

I can now build a dll

I can run lua -luatrace

I can require"luatrace" if I assign it to a variable (local luatrace = require"luatrace" for example)

I get a trace-out.txt file when i run luatrace

BUT

when i then want to analyse it i run the command lua -luatrace.profile trace-out.txt (is this the correct way?)

and get the following output:

>lua -luatrace.profile trace-out.txt

lua: trace-out.txt:1: unexpected symbol near '>'

Total time     0 nanoseconds

Times in nanoseconds

Top 20 lines by total time

File:line  Hits  Total   Self  Child | Line

Top 20 functions by self time

File:lines  Hits  Total   Self  Child | Line

I hope this is not what I'm supposed to get

On Fri, Oct 7, 2011 at 2:48 PM, Oskar Forsslund <matrixsmurfen@googlemail.com> wrote:

ok... there was some error which led to my previious post but now i cannot reproduce it.

I think I understand why the aforementioned lines look like they do, it has something to do with not forcing luatrace into the global scope

please disregard my previous post for now  =)

On Fri, Oct 7, 2011 at 2:18 PM, Oskar Forsslund <matrixsmurfen@googlemail.com> wrote:

I found another possible bug!

i believe that line 171 should be: luaL_register(L, "luatrace.c_hook", hook_functions);

so that kook_functions is imported into luatrace.c_hook and not into its own table c_hook

line 21 in luatrace.lua suggests this since it tries to require luatrace.c_hook

On Thu, Oct 6, 2011 at 1:42 AM, Elias Barrionovo <elias.tandel@gmail.com> wrote:

For the record, gcc's man page does say that if you want to abort the
compiler if it finds anything not on the std you're using (through the
--std parameter) - not only C89 or C99 -, you must use -pedantic .

So I use it quite a lot. =)

On 10/5/11, Geoff Leyland <geoff_leyland@fastmail.fm> wrote:
> On 6/10/2011, at 10:05 AM, Luiz Henrique de Figueiredo wrote:
>
>> We also use -Wall -Wextra when compiling Lua.
>
> -Wextra gets the c++ comment (wouldn't it be nice if -Wall did what it
> said!)
>
> On 6/10/2011, at 9:56 AM, Sean Conner wrote:
>
>> I think you might want to try "gcc -pedantic -ansi" or "gcc -pedantic
>> -std=c89".
>
> and -pedantic gets the variable declaration in the middle of the block.
>
> Thanks!
>

--
Sent from my mobile device

NI!