Bug 115319 – crash when using MemoFile conduit

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 115319 - crash when using MemoFile conduit


Summary:	crash when using MemoFile conduit


Status:	RESOLVED DUPLICATE of bug 114361

Product:	gnome-pilot
Classification:	Other
Component:	conduit: memo_file
Version:	unspecified
Hardware:	Other other

Importance:	Normal critical
Target Milestone:	---
Assigned To:	gnome-pilot Maintainers
QA Contact:	gnome-pilot Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2003-06-16 21:12 UTC by Philip R. Schaffner
Modified:	2006-03-14 21:38 UTC

See Also:
GNOME target:	---
GNOME version:	---

Attachments
gdb output and stack trace (8.54 KB, text/plain) 2003-06-17 12:52 UTC, Philip R. Schaffner	Details

Description Philip R. Schaffner 2003-06-16 21:12:21 UTC

Package: gnome-pilot
Severity: major
Version: 2.0.9
Synopsis: crash when using MemoFile conduit
Bugzilla-Product: gnome-pilot
Bugzilla-Component: conduit: memo_file
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:
gnome-pilot consistently crashes if MemoFile conduit is enabled for any
Action

Steps to reproduce the problem:
1. Enable MemoFile conduit
2. Perform HotSync
3. 

Actual Results:
Gnome Application Crash Error pops up

Expected Results:
Backup or synchronize Memo Files

How often does this happen?
Every Time

Additional Information:
Was working before upgrade to gnome-pilot-2.0.9-0.ximian.6.2




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-06-16 17:12 -------

The original reporter (P.R.Schaffner@larc.nasa.gov) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, gnome-pilot-maint@bugzilla.gnome.org.

Comment 1 Elijah Newren 2003-06-17 04:15:39 UTC

Thanks for the bug report. Without a stack trace from the crash it's
very hard to determine what caused the crash. Please see
http://bugzilla.gnome.org/getting-traces.cgi for more information
about getting a useful stack trace.

Comment 2 Philip R. Schaffner 2003-06-17 12:52:32 UTC

Created attachment 17577 [details]
gdb output and stack trace

Comment 3 Elijah Newren 2003-06-17 15:14:15 UTC

This appears to be a unique stack trace, according to the
simple-dup-finder-dev.  I'm going to set all the fields appropriately
and reopen.  Also, I'm pasting the stack trace inline so that we can
catch duplicates more easily.  Note, however, that the attachment also
includes all messages since the start of the program in addition to
the stack trace, so it may still be useful to look at it in addition
to what I'm copying below:

(gdb) thread apply all bt

+ Trace 37889

Thread 1 (Thread 1086731616 (LWP 12618))

#0 ??
#1 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#2 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#3 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#4 gtk_signal_emit
from /usr/lib/libgtk-x11-2.0.so.0
#5 gnome_pilot_conduit_standard_abs_iterate_specific
from /usr/lib/libgpilotdconduit.so.2
#6 standard_abs_merge_to_remote
from /usr/lib/libgpilotdconduit.so.2
#7 gnome_pilot_conduit_standard_abs_new
from /usr/lib/libgpilotdconduit.so.2
#8 gnome_pilot_conduit_backup_restore
from /usr/lib/libgpilotdconduit.so.2
#9 g_cclosure_new_swap
from /usr/lib/libgobject-2.0.so.0
#10 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_emitv
from /usr/lib/libgobject-2.0.so.0
#13 gnome_pilot_conduit_standard_synchronize
from /usr/lib/libgpilotdconduit.so.2
#14 main
#15 main
#16 gpilot_sync_default
#17 device_equal_by_io
#18 device_equal_by_io
#19 device_equal_by_io
#20 device_in
#21 g_vsnprintf
from /usr/lib/libglib-2.0.so.0
#22 g_get_current_time
from /usr/lib/libglib-2.0.so.0
#23 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#24 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#25 g_main_context_iteration
from /usr/lib/libglib-2.0.so.0
#26 remove_pid_file
#27 main
#28 __libc_start_main
from /lib/tls/libc.so.6

Comment 4 Elijah Newren 2003-06-17 15:14:41 UTC

...and marking as new.

Comment 5 Philip R. Schaffner 2003-06-18 18:00:12 UTC

Appears to be duplicate of bug 114361 which has several other duplicates.

Comment 6 Matt Davey 2006-03-14 21:38:50 UTC


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