Mail Archives: djgpp/1999/06/27/06:56:07
Newsgroups: | comp.os.msdos.djgpp
|
From: | manfred DOT heumann AT uni-bielefeld DOT de (Manni Heumann)
|
Subject: | Allegro: install_mouse () hangs
|
X-Newsreader: | News Xpress 2.01
|
Date: | Sun, 27 Jun 1999 10:10:24 GMT
|
NNTP-Posting-Host: | ppp36-87.hrz.uni-bielefeld.de
|
Message-ID: | <3775f891.0@news.uni-bielefeld.de>
|
X-Trace: | 27 Jun 1999 12:10:25 +0200, ppp36-87.hrz.uni-bielefeld.de
|
Lines: | 31
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
Reply-To: | djgpp AT delorie DOT com
|
This is a strange problem, that just popped up in my program:
My program will hang, when Allegro's install_mouse() is called. I looked at
the sources, but I didn't see any possibilities for infinite loops. Could it
be, that the locking of variables that is done inside install_mouse() somehow
fails and this will produce the mentioned behavior?
Now, as if that weren't strange enough, this problem will not occur anytime
install_mouse() is called, but only when I pass more than one argument to my
program (i.e. argc>2).
I would post some code if I saw a way to chop my code down to the core of the
problem, but it's simply to big and I don't expect a little test program to
show that behavior. After all, install_mouse () has been working for years, no
matter how many arguments I passed to my programs.
Btw: All the Allegro install and init routines are called after my program has
been running for some time, thereby eating up some memory. Is there any
reason to call these routines as soon as possible after program start?
I am using Allegro 3.11 with gcc version egcs-2.91.66 19990314 (egcs-1.1.2
release) on Win95.
Any ideas anybody?
--
Manni
- Raw text -