| Re: [AD] al_stop/al_uninstall_timer later fails |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: "Coordination of admins/developers of the game programming library Allegro" <alleg-developers@xxxxxxxxxx>
- Subject: Re: [AD] al_stop/al_uninstall_timer later fails
- From: "Trent Gamblin" <trent@xxxxxxxxxx>
- Date: Wed, 21 Apr 2010 08:22:21 -0600 (MDT)
On Tue, April 20, 2010 8:17 pm, Peter Wang said:
> Is it possible to get a backtrace?
#0 0x34b9db84 in __semwait_signal
#1 0x34b64546 in pthread_join
#2 0x00005240 in _al_thread_join at uxthread.c:80
#3 0x00014a32 in al_stop_timer at timernu.c:253
#4 0x00014bc8 in al_uninstall_timer at timernu.c:187
#5 0x000213b0 in _al_mutex_lock [inlined] at aintuthr.h:86
#6 0x000213b0 in _al_run_destructors
#7 0x00014292 in al_uninstall_system at system_new.c:262
#8 0x34bc1950 in __cxa_finalize
#9 0x34b4ca24 in exit
#10 0x00005052 in user_main at iphone_main.m:35
#11 0x0001483e in thread_func_trampoline at threads.c:80
#12 0x00005136 in thread_proc_trampoline at uxthread.c:36
> It looks okay, other than the fact it's overkill :-P
> You could just use (al_current_time() - last_time).
>
> al_get_next_event() is non-blocking so checking al_event_queue_is_empty()
> is redundant.
Ok, point taken.
Trent :{)>