On Fri, 2004-01-16 at 12:42, Leopold Toetsch wrote:

> Ah yep. When committing the first (trial) fix, I thought about such
> a problem, which is related:
> - if it seems to hang on a condition variable (still AFAIK: it shouldn't)

It reminds me of a problem I'm having with MySQL, actually.

>   - but anyway - it could depend on objects, that need destruction, like
>     a timer event, so ...
> 
> I moved killing the event loop a bit down in the interpreter destroy
> sequence. Reaching that point, timers should be removed from the queue.

This gets further.  Now it's imcc/t/syn/macro, around tests 13 and 14:

#0  0x0ff976a4 in __pthread_sigsuspend () from /lib/libpthread.so.0
#1  0x0ff973e0 in __pthread_wait_for_restart_signal ()
   from /lib/libpthread.so.0
#2  0x0ff96fe4 in pthread_onexit_process () from /lib/libpthread.so.0
#3  0x0fd0a694 in exit () from /lib/libc.so.6
#4  0x101a730c in fataly (code=1, file=0x102b66f7 "M", lin=6, 
    fmt=0x1021ae9c "Macro '%s' requires %d arguments, but %d given")
    at imcc/debug.c:34
#5  0x1019c940 in expand_macro (valp=0x7fffed30, interp=0x10273e98, 
    name=0x102b66f7 "M") at imcc.l:731
#6  0x101996f4 in yylex (valp=0x7fffed30, interp=0x10273e98) at
imcc.l:349
#7  0x10193e50 in yyparse (interp=0x10273e98) at imcc/imcparser.c:1611
#8  0x10031d34 in main (argc=1, argv=0x7ffff5b0) at imcc/main.c:493

and a similar one in imcc/t/sym/clash, around test 9:

#0  0x0ff976a4 in __pthread_sigsuspend () from /lib/libpthread.so.0
#1  0x0ff973e0 in __pthread_wait_for_restart_signal ()
   from /lib/libpthread.so.0
#2  0x0ff96fe4 in pthread_onexit_process () from /lib/libpthread.so.0
#3  0x0fd0a694 in exit () from /lib/libc.so.6
#4  0x101a730c in fataly (code=1, file=0x7ffff756
"imcc/t/syn/clash_9.imc", 
    lin=2, fmt=0x10216920 "Unknown PMC type '%s'\n") at imcc/debug.c:34
#5  0x101953b4 in yyparse (interp=0x10273e98) at imcc.y:694
#6  0x10031d34 in main (argc=1, argv=0x7ffff5b0) at imcc/main.c:493

Would you like me to keep reporting them as I find them?  Looking at the
source code of fataly, there's a TODO comment just above the culprit.

-- c

Reply via email to