GNOME Bugzilla – Bug 356548
crash in PalmOS Devices: I started the gpilotd-co...
Last modified: 2006-10-25 14:51:27 UTC
What were you doing when the application crashed? I started the gpilotd-control-applet and tried to get the PDA Identification from the PDA. I use a Palm T5 Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.0 2006-09-04 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 60137472 vsize: 0 resident: 60137472 share: 0 rss: 14217216 rss_rlim: 0 CPU usage: start_time: 1158590730 rtime: 0 utime: 166 stime: 0 cutime:155 cstime: 0 timeout: 11 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gpilotd-control-applet' (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 -1224964432 (LWP 5591)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 72651
Thread 1 (Thread -1224964432 (LWP 5591))
Thanks for the bug report. Without a stack trace from the crash it's very hard to determine what caused it. Can you provide us with one? Please see http://live.gnome.org/GettingTraces for more information on how to do so. In addition, it would be useful to know what version of gnome-pilot and pilot-link you are using. Finally for now, it would be good to know if this bug is reproducible. Does it happen every time you try to run the gpilotd-control-applet?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information Matt asked for. Thanks!