GNOME Bugzilla – Bug 159506
Gpilotd's conduit "Backup" crashes when backing up "ImgFile-Foto" on a PalmOne Tungsten E
Last modified: 2006-03-13 22:52:26 UTC
Distribution: Debian 3.1 Package: gnome-pilot Severity: normal Version: GNOME2.6.1 2.0.10 Gnome-Distributor: Debian Synopsis: Gpilotd's conduit "Backup" crashes when backing up "ImgFile-Foto" on a PalmOne Tungsten E Bugzilla-Product: gnome-pilot Bugzilla-Component: conduit: backup Bugzilla-Version: 2.0.10 BugBuddy-GnomeVersion: 2.0 (2.6.1.1) Description: Description of the crash: Gpilotd "exits unexpectedly" when backing up "ImgFile-Foto" from my PalmOne Tungsten E Steps to reproduce the crash: 1. Run gpilotd 2. Attach the palmpilot to the computer 3. Perform a normal hotsync with the backup conduit enabled. Expected Results: All files backed up, successfull hotsync according to the palmpilot. How often does this happen? Every time Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gpilotd' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 1088493792 (LWP 5180)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x40a9d40e in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 52677
Thread 1 (Thread 1088493792 (LWP 5180))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-11-25 20:18 ------- Unknown version 2.0.10 in product gnome-pilot. Setting version to "unspecified". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-pilot". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was julian.calaby@gmail.com. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Matches the stack trace in bug 166119, but unfortunately that stack trace is not very useful in determining the cause of the crash. Please make sure that the package was compiled with debugging symbols and see http://bugzilla.gnome.org/getting-traces.cgi for more information about useful stack traces.
I am running Debian and the only way I can get proper debugging output is to compile my own modules and everything, which is more effort than I'm willing to go to, (Especailly as I'd have to download the source, not an easy task on 56K dialup) Sorry. However, if anyone else out there has a Tungsten E, and is willing to install Palm Photo on it, it should crash the exact same way. (I can give you version numbers if you need them) I have tried this many times, with different applications on it, and after removing the offending file. Removing it (and other files, ask me for a complete list if you need it) allowed GPilotd to complete successfully. I have no real information on this, but I suspect that these files have large record sizes, or something else non-standard which is messing with GPilotd. Apart from proper stack traces, I am willing to give any help I can to fixing this. (Or testing other parts of GPilotd)
Appears to be a duplicate of the >64k segment pilot-link bug. *** This bug has been marked as a duplicate of 136010 ***