suse linux 10.1, allegro library 4.2.0 blocks at exit if:
1. launched opening new console (launched from midnight
commander)
2. timer active (install_timer called).
No problem if launched fromm command prompt, or
install_timer not called.
Test program is the simplest possible.
Details: See the readme.txt from atachment,
allegro program in altest directory
test in tmp directory.
test files and readme.txt
Logged In: YES
user_id=32894
Thanks for the detailed report and test case.
I cannot reproduce the problem here though. Debian linux,
allegro SVN, started the test from either gnome-terminal or
nautilus, and both times it closed after some seconds.
The non-Allegro test seemed to hang though.. but I'm not
sure I can follow how it relates to the Allegro test,
without spending some more time on it.
So, I don't know.. can you describe how to fix this inside
Allegro, or maybe submit a complete patch?
Logged In: YES
user_id=1542934
I think You can not reproduce the blocking because you tried
from the X Windows system.
I'm using console mode (framebuffer device VESA VGA mode 791
(1024x768x16)).
The non allegro test is made to reproduce the problem (I
watched what is happening in the allegro application when
the test program runs (I watched the fork in lconsole.c, and
thread creation in uthreads.c and uptimer.c) and I made the
non allegro program with minimal uthreads.cpp and
uptimer.cpp to reproduce the error.
For the error to appear it is necessary that in lconsole.c
in allegro the test
"if (__al_linux_vt != 0)"
to be false to create new console.
for this reason need the allegro application be launched
from Midnight Commander, and not dirrectly from command prompt.
Unfortunately I do not know what to do with this error,
I think it is not an Allegro error, but maybe some body
knows a workaround for this.