vellum wrote:
Hi Bob and others, The Gtk-critical messaage that I reported a couple of days ago is still coming up all the time for me. Latest build (11th Oct) still has it.
cheers, vellum.
Heh! Well, reminding won't help. ;-) What -would- help would be if you could run Inkscape.exe in gdb, and put a breakpoint on that line #. We could find the problem a lot faster that way, and it would be much appreciated. It would be something like this:
(Fyi: Inkscape_stripped.exe is fairly useless for testing purposes.)
c:\inkscape> gdb inkscape.exe GNU gdb 6.2 Copyright 2004 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 "i686-pc-mingw".
(gdb) break gtksystemwin32.c:578 No source file named gtksystemwin32.c. Make breakpoint pending on future shared library load? (y or [n]) y <---ONLY IF IT ASKS
Breakpoint 1 (gtksystemwin32.c:578) pending. (gdb) run Starting program: /home/rjamison/ink/inkscape/src/inkscape [New Thread -150388064 (LWP 8506)]
...when it hits that line, it -should- stop. When that happens, at the prompt type:
(gdb) bt
Then send the output to this list. It will help us immensely in finding the cause of that message. If it doesn't stop the program, well, you tried, and we appreciate the effort.
Thanks!
Bob