Hello again,
I have found a bug in the threads test.
Running a spinning worker results in a SIGABRT.
Libagar with debug enabled reports (among other
things):
Fatal error: AG_WidgetDraw() on unattached widget
A gdb backtrace reveals:
(gdb) bt
#0 0x00007ffff51adf85 in raise () from /lib/libc.so.6
#1 0x00007ffff51af408 in abort () from /lib/libc.so.6
#2 0x00007ffff71060f0 in AG_FatalError (
fmt=0x7ffff7431210 "AG_WidgetDraw() on unattached widget") at error...c:258
#3 0x00007ffff737f0ea in AG_WidgetDraw (p=0x7f98e0) at widget.c:1203
#4 0x00007ffff738423b in Draw (obj=0x7f36c0) at window.c:698
#5 0x00007ffff737f191 in AG_WidgetDraw (p=0x7f36c0) at widget.c:1216
#6 0x00007ffff7368613 in SDLFB_RenderWindow (win=0x7f36c0) at drv_sdlfb.c:183
#7 0x00007ffff7365c14 in AG_WindowDraw (win=0x7f36c0) at window.h:268
#8 0x00007ffff7365daf in AG_WindowDrawQueued () at window.h:306
#9 0x00007ffff7367daf in AG_SDL_EventEpilogue (es=0x682900, event=0x682920)
at drv_sdl_common.c:904
#10 0x00007ffff71109f2 in AG_EventLoop () at event.c:1481
#11 0x0000000000408f5e in main (argc=3, argv=0x7fffffffeb58) at agartest.c:559
I used the sdlfb driver, but this bug occurs with
the glx and sdlgl drivers as well.
Unfortunately I am not familiar enough with libagar
to debug this any further.
pap
_______________________________________________
Agar mailing list
[email protected]
http://libagar.org/lists.html
