Date: Fri, 16 Sep 2005 11:27:16 +0200 From: Stefano Zacchiroli To: LablGTK Mailing List Subject: stack backtrace for exceptions raised in callbacks Message-ID: <20050916092716.GB20173 at takhisis.invalid> Mail-Followup-To: LablGTK Mailing List Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Setting OCAMLRUNPARAM=b is very useful for debugging unexpected exceptions, but I'm unable to make it work for exceptions raised in callback. lablgtk2 exception handler catch every exceptions and print them using Printexc.to_string, thus the whole program wont quit due to uncaught exception. Setting my own user handler wont work either since the default lablgtk2 handler is tried anyway after mine. Is there a way to make a lablgtk program die for uncaught exception raised in callback? Note that I don't care about possible gtk2 memory leaks since the program is going to die, I'm just trying to use the ocamlrun backtrace debugging facility ... TIA, Cheers. -- Stefano Zacchiroli -*- Computer Science PhD student @ Uny Bologna, Italy zack@{cs.unibo.it,debian.org,bononia.it} -%- http://www.bononia.it/zack/ If there's any real truth it's that the entire multidimensional infinity of the Universe is almost certainly being run by a bunch of maniacs. -!-