Hi.
I've called my fresh backport from the command line today. Here I see these messages.
(geany:10536): GLib-CRITICAL **: g_key_file_set_string: assertion `string != NULL' failed (geany:10536): GLib-CRITICAL **: g_key_file_set_string: assertion `string != NULL' failed (geany:10536): GLib-CRITICAL **: g_key_file_set_string: assertion `string != NULL' failed (geany:10536): GLib-CRITICAL **: g_key_file_load_from_file: assertion `file != NULL' failed
What's the reason for them? My backport? Or the old configuration file of my previous Geany 0.12?
On Thu, 8 May 2008 07:33:30 +0200 Joerg Desch jd.vvd@web.de wrote:
Hi.
I've called my fresh backport from the command line today. Here I see these messages.
(geany:10536): GLib-CRITICAL **: g_key_file_set_string: assertion `string != NULL' failed (geany:10536): GLib-CRITICAL **: g_key_file_set_string: assertion `string != NULL' failed (geany:10536): GLib-CRITICAL **: g_key_file_set_string: assertion `string != NULL' failed (geany:10536): GLib-CRITICAL **: g_key_file_load_from_file: assertion `file != NULL' failed
What's the reason for them? My backport? Or the old configuration file of my previous Geany 0.12?
It's difficult to tell (I don't get them here). Possibly a configuration file is missing. Could you try getting a backtrace with gdb set to abort on GLib warnings:
gdb `which geany` r --g-fatal-warnings
Then when gdb stops type: bt full
And please send us everything from the run (r) command, thanks.
Regards, Nick
On Thu, 8 May 2008 12:30:17 +0100 Nick Treleaven nick.treleaven@btinternet.com wrote:
First I have to say, that geany is up and running. No matter of these messages.
gdb `which geany` r --g-fatal-warnings
$ gdb `which geany` GNU gdb 6.6-debian Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i486-linux-gnu"... (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (gdb) r --g-fatal-warnings Starting program: /usr/bin/geany --g-fatal-warnings (no debugging symbols found) (no debugging symbols found) .... [Thread debugging using libthread_db enabled] [New Thread -1220277696 (LWP 12503)] (no debugging symbols found) .... ....and geany is running.
Then when gdb stops type: bt full
Because there is no crash, I can't get a backtrace.
On Thu, 8 May 2008 13:31:28 +0200 Joerg Desch jd.vvd@web.de wrote:
On Thu, 8 May 2008 12:30:17 +0100 Nick Treleaven nick.treleaven@btinternet.com wrote:
...
Then when gdb stops type: bt full
Because there is no crash, I can't get a backtrace.
OK, but the --g-fatal-warnings option should make Geany abort when GLib issues those warnings, so gdb would stop. But as there were no warnings that time, perhaps they only occur on the first run of Geany. Possibly it's due to different settings in configuration files that confuses Geany.
Regards, Nick
On Thu, 8 May 2008 12:52:09 +0100 Nick Treleaven nick.treleaven@btinternet.com wrote:
But as there were no warnings that time, perhaps they only occur on the first run of Geany. Possibly it's due to different settings in configuration files that confuses Geany.
You are right. After playing with filetypes.common, I can't see these messages anymore.