GNOME Bugzilla – Bug 400218
crash in PalmOS Devices: essai d'enregistrement ...
Last modified: 2007-01-25 13:18:34 UTC
What were you doing when the application crashed? essai d'enregistrement de mon palm m105 dans gnome-pilot Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 36818944 vsize: 0 resident: 36818944 share: 0 rss: 14102528 rss_rlim: 0 CPU usage: start_time: 1169649426 rtime: 0 utime: 143 stime: 0 cutime:134 cstime: 0 timeout: 9 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 -1226266320 (LWP 6872)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 104860
Thread 1 (Thread -1226266320 (LWP 6872))
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance! Nothing in gnome_pilot_pdialog_get_type() calls g_free() so I can't see how this backtrace could be valid...
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. An official update for Edgy may be in the works, but you can download an unofficial one if you like. See comment # 14 in the duplicate bug. Kjartan: this stack trace has be dup'ed many times... The trace appears odd due to optimisation, as far as I was ever able to tell. *** This bug has been marked as a duplicate of 365181 ***