Re: Debug glibmm-CRITICAL
- From: Kjell Ahlstedt <kjellahlstedt gmail com>
- To: Emil Nowak <emiml wp pl>
- Cc: gtkmm-list gnome org
- Subject: Re: Debug glibmm-CRITICAL
- Date: Tue, 15 Dec 2020 10:16:21 +0100
On 2020-12-15 07:31,
Emil Nowak via gtkmm-list wrote:
Hello,
In my application from time to time I get "glibmm-CRITICAL" errors. They are
displayed on console.
I wonder how can I debug them.
So far I found that in glib there is env variable "G_DEBUG=fatal-criticals"
for that in Glib, but seems it doesn't affect Glibmm.
Is there anything similar in glibmm/gtkmm
I'm using:
Glibmm: 2.64.2
Gtkmm: 3.24.2
Run your application in a debugger, such as gdb, and
set a breakpoint at calls to the g_log function. Check from where
that function is called. There may be both interesting and
uninteresting calls to g_log().
[
Date Prev][
Date Next] [
Thread Prev][Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]