我试图在调试器中运行它,尝试在程序失败时执行’bt’.但它没有显示导致CRITICAL的代码在哪里:
(process:3155): Glib-GObject-CRITICAL **: /build/buildd/glib2.0-2.22.3/gobject/gtype.c:2458: initialization assertion Failed,use IA__g_type_init() prior to this function(process:3155): Glib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' Failed(process:3155): Glib-GObject-CRITICAL **: /build/buildd/glib2.0-2.22.3/gobject/gtype.c:2458: initialization assertion Failed,use IA__g_type_init() prior to this function(process:3155): Glib-GObject-CRITICAL **: /build/buildd/glib2.0-2.22.3/gobject/gtype.c:2458: initialization assertion Failed,use IA__g_type_init() prior to this function(process:3155): Glib-GObject-CRITICAL **: g_type_add_interface_static: assertion `G_TYPE_IS_INSTANTIAtable (instance_type)' Failed(process:3155): Glib-GObject-CRITICAL **: /build/buildd/glib2.0-2.22.3/gobject/gtype.c:2458: initialization assertion Failed,use IA__g_type_init() prior to this function解决方法 你可以打破g_log然后从那里做回溯. 总结
以上是内存溢出为你收集整理的linux – 如何找出导致GLib-GObject-CRITICAL的代码在哪里?全部内容,希望文章能够帮你解决linux – 如何找出导致GLib-GObject-CRITICAL的代码在哪里?所遇到的程序开发问题。
如果觉得内存溢出网站内容还不错,欢迎将内存溢出网站推荐给程序员好友。
欢迎分享,转载请注明来源:内存溢出
评论列表(0条)