On Thursday 13. August 2009 18:46:45 Rolando Abarca wrote: > Maybe rb_obj_respond_to is not "signal-safe"? It's been running for > about 20 minutes no crash so far. Are you running the Ruby interpreter from inside a signal handler ? If so, don't do that :-) The signal handler has its own environment (the original environment had to be saved so you return to the exact location after handling the signal). One may only call async-safe functions inside signal handlers, for a list see the following page (scroll down to the end): http://www.opengroup.org/onlinepubs/000095399/functions/xsh_chap02_04.html You would need to find another way to respond to the signal, like setting a variable and periodically check for it in your main loop or something like that. Marc -- Marc Haisenko Senior Developer Comdasys AG Rüdesheimer Str. 7 80686 Munich Germany Tel: + 49 (89) 548 4333 21 Fax: + 49 (89) 548 4333 29 eMail: haisenko / comdasys.com Web: www.comdasys.com registered in Munich HRB 150387 VAT-ID: DE 234430556 WEEE-Reg.: DE 56162020 Vorstand: Dipl. Inf. Martin Bitzinger Important notice: This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Comdasys AG. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error.