I'm having a problem running some gtk code. I encountered a problem
installing the Perl bindings to gtk but it seems to be related to the
underlying Suse gtk package. I built and ran the following C program:
/* gcc `pkg-config --libs --cflags gtk+-2.0` dialog.c -o dialog */
#include
int
main (int argc, char **argv)
{
GtkWidget *dialog;
gtk_init (&argc, &argv);
dialog = gtk_file_chooser_dialog_new ("Test",
NULL,
GTK_FILE_CHOOSER_ACTION_OPEN,
GTK_STOCK_CANCEL,
GTK_RESPONSE_CANCEL,
GTK_STOCK_OPEN,
GTK_RESPONSE_ACCEPT,
NULL);
gtk_widget_destroy (dialog);
return 0;
}
It runs to completion when run by a normal user, but hangs when run as
root. Furthermore, gdb complains about internal errors.
I'm not familiar with gdb but there's a log below. It hung when run, I
typed CTRL-C then when I did 'bt' it said there was an internal error in
gdb.
I tried again (see second log) and single-stepped main but it hung
immediately. The third log is the result of single-stepping as a normal
user.
I'm on an AMD 64 system with Suse 10.2. Has anybody seen anything like this? Can
anybody reproduce it?
Cheers, Dave
-------------------------------------------------------
# gdb dialog
GNU gdb 6.5
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 "x86_64-suse-linux"...Using host libthread_db
library "/lib64/libthread_db.so.1".
(gdb) run
Starting program: /home/dhoworth/progs/gtk/dialog-test/dialog
[Thread debugging using libthread_db enabled]
[New Thread 47081357781968 (LWP 20704)]
Program received signal SIGINT, Interrupt.
[Switching to Thread 47081357781968 (LWP 20704)]
0x00002ad1f9fe8a68 in __lll_mutex_lock_wait ()
from /lib64/libpthread.so.0
(gdb) bt
#0 0x00002ad1f9fe8a68 in __lll_mutex_lock_wait ()
from /lib64/libpthread.so.0
#1 0x00002ad1f9fe4a78 in _L_mutex_lock_106 ()
from /lib64/libpthread.so.0
dwarf2-frame.c:521: internal-error: Unknown CFI encountered.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)
-----------------------------------------------------------------
[as root]
(gdb) break main
Breakpoint 1 at 0x40081c
(gdb) run
Starting program: /home/dhoworth/progs/gtk/dialog-test/dialog
[Thread debugging using libthread_db enabled]
[New Thread 47972515281872 (LWP 20742)]
[Switching to Thread 47972515281872 (LWP 20742)]
Breakpoint 1, 0x000000000040081c in main ()
(gdb) s
Single stepping until exit from function main,
which has no line number information.
Program received signal SIGINT, Interrupt.
---------------------------------------------------------------------
[as normal user]
(gdb) break main
Breakpoint 1 at 0x40081c
(gdb) run
Starting program: /home/dhoworth/progs/gtk/dialog-test/dialog
[Thread debugging using libthread_db enabled]
[New Thread 47618411293648 (LWP 20761)]
[Switching to Thread 47618411293648 (LWP 20761)]
Breakpoint 1, 0x000000000040081c in main ()
(gdb) s
Single stepping until exit from function main,
which has no line number information.
[New Thread 1082132800 (LWP 20762)]
[New Thread 1090525504 (LWP 20763)]
0x00002b4f05442ae4 in __libc_start_main () from /lib64/libc.so.6
(gdb)
--
To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org
For additional commands, e-mail: opensuse+help@opensuse.org
