GNOME Bugzilla – Bug 477641
crash in Text Editor: printing a C header file
Last modified: 2007-09-21 19:35:50 UTC
Version: 2.18.2 What were you doing when the application crashed? printing a C header file Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 73711616 vsize: 73711616 resident: 34283520 share: 22081536 rss: 34283520 rss_rlim: 4294967295 CPU usage: start_time: 1189992408 rtime: 3692 utime: 3455 stime: 237 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gedit' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208588576 (LWP 7648)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 163446
Thread 1 (Thread -1208588576 (LWP 7648))
No plugin installed in $HOME. Module versions: - glib 2.12.13 - gtk+ 2.10.14 - gtksourceview - libgnomeui 2.18.1 - libglade 2.6.0 - libgnomeprintui 2.18.0 - gnome-vfs 2.18.1 - pygobject 2.12.3 - pygtk 2.10.6 - gnome-python - gnome-python-desktop 2.18.0 - enchant - iso-codes Python module versions: - python 2.5 - pygtk 2.10.6 (GTK+ 2.10.14) - gnome-python 2.18.1 ----------- .xsession-errors (3860 sec old) --------------------- /home/jr/projects/hamming10/hamming10/HammingLib1.c:684: warning: format ‘%I64u’ expects type ‘unsigned int’, but argument 3 has type ‘ULONG64’ /home/jr/projects/hamming10/hamming10/HammingLib1.c:683: warning: format ‘%I64u’ expects type ‘unsigned int’, but argument 3 has type ‘ULONG64’ /home/jr/projects/hamming10/hamming10/HammingLib1.c:682: warning: format ‘%I64u’ expects type ‘unsigned int’, but argument 3 has type ‘ULONG64’ /home/jr/projects/hamming10/hamming10/HammingLib1.c:681: warning: format ‘%I64u’ expects type ‘unsigned int’, but argument 3 has type ‘ULONG64’ /home/jr/projects/hamming10/hamming10/HammingLib1.c:680: warning: format ‘%I64u’ expects type ‘unsigned int’, but argument 3 has type ‘ULONG64’ /home/jr/projects/hamming10/hamming10/HammingLib1.c:677: warning: format ‘%I64u’ expects type ‘unsigned int’, but argument 3 has type ‘ULONG64’ /home/jr/projects/hamming10/hamming10/HammingLib1.c:676: warning: format ‘%I64u’ expects type ‘unsigned int’, but argument 3 has type ‘ULONG64’ /home/jr/projects/hamming10/hamming10/HammingLib1.c:672: warning: too few arguments for format /home/jr/projects/hamming10/hamming10/HammingLib1.c:670: warning: implicit declaration of function ‘fopen_s’ /home/jr/projects/hamming10/hamming10/HammingLib1.c: In function ‘SaveState’: /home/jr/projects/hamming10/hamming10/HammingLib1.c:607: warning: format ‘%I64u’ expects type ‘unsigned int’, but argument 2 has type ‘ULONG64’ /home/jr/projects/hamming10/hamming10/HammingLib1.c:606: warning: format ‘%I64u’ expects type ‘unsigned int’, but argument 2 has type ‘ULONG64’ /home/jr/projects/hamming10/hamming10/HammingLib1.c:605: warning: format ‘%I64u’ expects type ‘unsigned int’, but argument 2 has type ‘ULONG64’ /home/jr/projects/hamming10/hamming10/HammingLib1.c:604: warning: format ‘%I64u’ expects type ‘unsig ...Too much output, ignoring rest... --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 405900 ***