Joe Sislow:
Yeah, I ran that and it just spit up the same error. Is there a debug command I can enable thru configure or something to have it spit more info when it dies?
Run inside gdb; break on gdk_x_error; print a backtrace. Here is an example run although I have used gdk_cursor_new as that is hit early in a run: you should type gdk_x_error where I have gdk_cursor_new: [EMAIL PROTECTED]:~$ gdb SciTE 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"... Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (gdb) break gdk_cursor_new Function "gdk_cursor_new" not defined. Make breakpoint pending on future shared library load? (y or [n]) y Breakpoint 1 (gdk_cursor_new) pending. (gdb) run --sync Starting program: /usr/bin/SciTE --sync [Thread debugging using libthread_db enabled] [New Thread -1219798416 (LWP 6424)] Breakpoint 2 at 0xb7b5ba76 Pending breakpoint "gdk_cursor_new" resolved [Switching to Thread -1219798416 (LWP 6424)] Breakpoint 2, 0xb7b5ba76 in gdk_cursor_new () from /usr/lib/libgdk-x11-2.0.so.0 (gdb) bt #0 0xb7b5ba76 in gdk_cursor_new () from /usr/lib/libgdk-x11-2.0.so.0 #1 0x0808bfee in ScintillaGTK::RealizeThis () #2 0x0808c1d2 in ScintillaGTK::Realize () #3 0xb78e59d9 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 #4 0xb78d6e49 in ?? () from /usr/lib/libgobject-2.0.so.0 #5 0x0818af18 in ?? () #6 0x00000000 in ?? () (gdb) Neil _______________________________________________ Scite-interest mailing list [email protected] http://mailman.lyra.org/mailman/listinfo/scite-interest
