On Wed, May 02, 2007 at 10:43:15PM +0200, Wichert Akkerman wrote: > Previously Florian Ragwitz wrote: > > xmms2 just calls g_error (a glib function) which purpose is to log a > > fatal error and terminate the application by calling abort(). Should > > glib be fixed? > > Or perhaps g_error should not be used. I'm guessing g_error is meant to > be used when something so bad happend the code can no longer even expect > to show an error message to the user using its normal user interface. > For example when catching a SIGSEGV or SIGBUS. > > That is not the case here; a normal error message to stdout and a > non-zero exit code work fine.
ok, I agree. I'll fix this issue in my tree and try to get it merged into xmms2-devel. -Flo -- BOFH excuse #400: We are Microsoft. What you are experiencing is not a problem; it is an undocumented feature.
signature.asc
Description: Digital signature
