After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 332920 - gpilotd sigfaults during backup hotsync
gpilotd sigfaults during backup hotsync
Status: RESOLVED DUPLICATE of bug 136010
Product: gnome-pilot
Classification: Other
Component: conduit: backup
unspecified
Other other
: High critical
: ---
Assigned To: gnome-pilot Maintainers
gnome-pilot Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-03-01 00:17 UTC by Monaco, F. J.
Modified: 2006-03-01 02:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8


Description Monaco, F. J. 2006-03-01 00:17:41 UTC 
From:  <>
To: submit@bugs.gnome.org
X-Mailer: bug-buddy 2.8.0
Subject: gpilotd crashes when it tries to backup Blazer files

Distribution: Debian 3.1
Package: gnome-pilot
Severity: critical
Version: GNOME2.8.3 unspecified
Gnome-Distributor: Debian
Synopsis: gpilotd crashes when it tries to backup Blazer files
Bugzilla-Product: gnome-pilot
Bugzilla-Component: conduit: backup
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.8.1)
Description:
Description of the crash:
During the hotsync, with only backup conduit enabled, gpilotd makes
backups of serveral files and suddenly craches when getting Blazer (web
browser) files. 

Steps to reproduce the crash:
1. run gpilotd in the console
2. start hotsync
3. wait until it craches

Expected Results:
gpilotd crashe

How often does this happen?
Always

Additional Information:
It works perfectly, though, in that other OS. 
Other conduits seems to work fine.

I have read about the >64k bug and, so I checked my
backup directory and saw that pilot-link was able to handle larger
files (there were several files larger than 64k).  Blazer files are
smaller. 
I was unable to find out what file caused the problem.

This the the tail of gdb output:

backupconduit-Message: Wrote 336 of 336 resources, which is good
backupconduit-Message: Making backup of Blazer

---Type <return> to continue, or q <return> to quit---
Program received signal SIGSEGV, Segmentation fault.

+ Trace 66589

Thread NaN (LWP 11820)

  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 dlp_exec
    from /usr/lib/libpisock.so.8
  • #4 dlp_ReadResourceByIndex
    from /usr/lib/libpisock.so.8
  • #5 ??
    from /usr/lib/gnome-pilot/conduits/libbackup_conduit.so
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
    from /usr/lib/gnome-pilot/conduits/libbackup_conduit.so
  • #15 ??
    from /usr/lib/gnome-pilot/conduits/libbackup_conduit.so
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 free
    from /lib/tls/libc.so.6
  • #23 gnome_pilot_conduit_file_install_db
    from /usr/lib/libgpilotdconduit.so.2
  • #24 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #25 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #26 g_signal_emitv
    from /usr/lib/libgobject-2.0.so.0
  • #27 gnome_pilot_conduit_backup_backup
    from /usr/lib/libgpilotdconduit.so.2
  • #28 main 




------- Bug created by bug-buddy at 2006-03-01 00:17 -------
Comment 1 Karsten Bräckelmann 2006-03-01 02:40:33 UTC 
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.


Same stacktrace as bug 302317, which is a duplicate of bug 136010.

*** This bug has been marked as a duplicate of 136010 ***