GNOME Bugzilla – Bug 384786
crash in Time and Date: i just runned the comman...
Last modified: 2006-12-12 05:01:44 UTC
Version: 2.15.5 What were you doing when the application crashed? i just runned the command time at the terminal!and then it crashed. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 38490112 vsize: 0 resident: 38490112 share: 0 rss: 15753216 rss_rlim: 0 CPU usage: start_time: 1165860942 rtime: 0 utime: 4494 stime: 0 cutime:4413 cstime: 0 timeout: 81 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/time-admin' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225766512 (LWP 11389)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 93333
Thread 1 (Thread -1225766512 (LWP 11389))
Could you please add this line to your /etc/apt/sources.list: deb http://people.ubuntu.com/~pitti/ddebs edgy main universe install libgtk2.0-0-dbgsym, libglib2.0-0-dbgsym, liboobs-1-2-dbgsym and gnome-system-tools-dbgsym, and try to reproduce again the crash? after installing those packages, here are the command line instructions to get a backtrace: $ gdb time-admin (gdb) r ...wait for SIGSEGV... (gdb) thread apply all bt copy the output to a file and attach it here, please. Take into account that I can't reproduce this bug, so I need some help :)
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 358747 ***