Benjamin Ducke wrote: > Which leads to option 2: create a global variable that controls whether > fatal errors should trigger an exit() or not and make all GRASS C API > functions that potentially call G_fatal_error() respect this. > However, I think this may create a lot of unpredictable behaviour (!?) > > Maybe it would be enough to modify G_fatal_error() in that case?
Have a look at G_set_error_routine() in lib/gis/error.c but G_fatal_error() still ends with exit(EXIT_FAILURE). Hamish __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ grass-dev mailing list grass-dev@grass.itc.it http://grass.itc.it/mailman/listinfo/grass-dev
