解决Gtk-CRITICAL报错：gdb参数无效及g_log断点失效问题

Hey there! Let's walk through what you might be missing here to track down those Gtk-CRITICAL errors:

1. --g-fatal-warnings is a program argument, not a gdb option #

That error you're seeing makes total sense—--g-fatal-warnings isn't a flag for gdb itself, it's a runtime parameter for Gtk-based applications. It tells Gtk to treat critical warnings as fatal errors (which will crash the program, making it easier to catch in gdb).

To use it correctly:

• Either run your program directly with the flag:

  ./dbhandler --g-fatal-warnings
  

• Or load your program into gdb first, then pass the flag when starting the program:

  gdb ./dbhandler
  # Inside gdb:
  run --g-fatal-warnings
  

2. g_log might not be the right function to break on #

Gtk's logging system often uses lower-level functions under the hood, so setting a breakpoint on g_log alone might not catch the critical warnings. Try these alternatives:

• Set a breakpoint on g_logv (most logging calls eventually route through this function):

  break g_logv
  

• Target critical-specific functions like g_critical or gtk_critical directly:

  break g_critical
  

• Make sure your program and Gtk libraries have debug symbols installed. If you compiled your program without the -g flag, recompile it with debugging info enabled. For system-wide Gtk libraries, you may need to install your distribution's debug symbol package (e.g., something like libgtk-3-0-dbg on Debian/Ubuntu-based systems) to get meaningful breakpoints.

3. Add more context with debug logging #

Before diving into gdb, you can get more detailed info about where the critical warning is coming from by setting the G_MESSAGES_DEBUG environment variable:

G_MESSAGES_DEBUG=all ./dbhandler

This will print verbose logs that can point you directly to the code path causing the issue, which might save you from needing to debug with gdb at all.

内容的提问来源于stack exchange，提问作者Igor