don't do queries on error, we don't get many errors these days for which it is useful tell us which scheduler we're n...

Original commit message from CVS:
don't do queries on error, we don't get many errors these days for which
it is useful
tell us which scheduler we're not finding
This commit is contained in:
Thomas Vander Stichele 2002-12-16 09:50:40 +00:00
parent 80cc767749
commit 84e121f4dd
2 changed files with 8 additions and 4 deletions

View file

@ -70,7 +70,9 @@ debug_log_handler (const gchar *log_domain,
gpointer user_data) gpointer user_data)
{ {
g_log_default_handler (log_domain, log_level, message, user_data); g_log_default_handler (log_domain, log_level, message, user_data);
g_on_error_query (NULL); /* FIXME: do we still need this ? fatal errors these days are all
* other than core errors */
/* g_on_error_query (NULL); */
} }
enum { enum {

View file

@ -108,9 +108,11 @@ gst_pipeline_init (GstPipeline *pipeline)
/* FIXME need better error handling */ /* FIXME need better error handling */
if (scheduler == NULL) { if (scheduler == NULL) {
g_error ("Critical error: could not get a scheduler - \ const gchar *name = gst_scheduler_factory_get_default_name ();
are you sure you have a registry ? Run gst-register as root \
if you haven't done so yet."); g_error ("Critical error: could not get scheduler \"%s\"\n"
"Are you sure you have a registry ?\n"
"Run gst-register as root if you haven't done so yet.", name);
} }
} }