At 1242331287 time_t, Uli Schlachter wrote:
> And another backtrace, this time with gdb...
> The plan for is to finally use "-O0 -fno-inline" and see what happens. (btw 
> yay,
> finally done with school and I got time for this!) (Oh and another btw: I 
> still
> don't know any way to reproduce this, it just happens :( )
> 
> 
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7fe166b55740 (LWP 4868)]
> 0x00000032a5c7d4dc in ?? () from /lib/libc.so.6
> #0  0x00000032a5c7d4dc in ?? () from /lib/libc.so.6
> No symbol table info available.
> #1  0x00000032a5c7b92c in memmove () from /lib/libc.so.6
> No symbol table info available.
> #2  0x0000000000439e25 in luaA_imagebox_newindex (L=0x26e10b0, token=<value
> optimized out>) at /home/ancient/jd/Work/debian/awesome/common/luaobject.h:39
>       buf = <value optimized out>
>       len = <value optimized out>
>       widget = (widget_t *) 0x2b3bcd8
>       d = (imagebox_data_t *) 0x2937550
> #3  0x0000000000430032 in luaA_widget_newindex (L=0x26e10b0) at
> /home/ancient/jd/Work/debian/awesome/widget.c:490
>       len = 5
>       widget = (widget_t *) 0x2b3bcd8
>       buf = <value optimized out>
>       token = A_TK_UNKNOWN

That's just weird. If the token is A_TK_UNKNOWN, it's because some code
is doing myimagebox.blabla = <value> where blabla is not a known
attribute, therefore we get A_TK_UNKNOWN as token.

Then it calls luaA_imagebox_newindex which does not handle A_TK_UNKNOWN
in its switch() statement, so it goes to default which return 0.

Where the hell memmove is called from lua object function, I don't see.

I suggest that next time you try to print some stuff and dig directly
into the code/debugger because I really miss what's wrong.

Thanks anyway :)

Cheers,
-- 
Julien Danjou
// ᐰ <jul...@danjou.info>   http://julien.danjou.info
// 9A0D 5FD9 EB42 22F6 8974  C95C A462 B51E C2FE E5CD
// Tomorrow I was nothing, yesterday I'll be.

Attachment: signature.asc
Description: Digital signature

Reply via email to