I also did a simple wrapper that encapsulate malloc and do kind of trace, but I would rather use g_malloc instead of malloc and use the maybe better memory check of the glib. Anyway if I can't change it, art least I know, thank you :-) I'll try to improve my own memchecker so. Thanks a lot :-)
> Hi Jean-Christophe, > > Unfortunately I don't think this is possible. You can use > g_log_set_fatal_mask() to say which sorts of errors are fatal, but > G_LOG_LEVEL_ERROR is always set fatal whatever you do. > > I think this was decided because for a GUI library, it's very hard to > recover reliably from out-of-mem errors. If you use glib for something > else, of course, this may not be the right decision. > > I have an image processing library which uses glib ... but I had to make > my own malloc() wrapper, as I needed to be able to recover from > out-of-mem errors. > > John > > Jean-Christophe Berthon wrote: > > > Another post that I hope you're not going to buried neither... I still don't > > really understand how not to make fatal warning with the GLib... Please > > help! > > > > > > > >>Hello, > >> > >>I would like to know if anybody knows how to use g_log () to set it to non > >>fatal warning (if a g_malloc fail, the application stop, I would rather > >> > > get > > > >>a returned error and deal with that). > > > > _______________________________________________ > gtk-list mailing list > [EMAIL PROTECTED] > http://mail.gnome.org/mailman/listinfo/gtk-list _______________________________________________ gtk-list mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/gtk-list
