Re: GnomeCal conduit errors

[Ken Scott <kscott-list pcisys net>]

On Tue, 7 Dec 1999, Eskil Heyn Olsen wrote:

> On Mon, 6 Dec 1999, Ken Scott wrote:
> 
> > gpilotd-Message: gpilotd: setting PILOTRATE=115200
> > gpilotd-WARNING **: pi_accept: Connection timed out
> > gpilotd-WARNING **: An error occured while getting the pilot's user data
> 
> This is new. This is during gnomecc's Get from Pilot ?
> 

This is while gpilotd is running, and I hit the hotsync button on the
cradle. It may be related to an issue I've seen with pilot-xfer where I
start the sync, but there is an immediate error from pilot-xfer and it
stops. I have to soft-reset my Pilot and then all is fine.

I also had strange goings-on when I was doing the Get From Pilot and Send
To Pilot buttons. Quite often, the IDs would change, and the User Name
would come back as garbage. I cleared out all of my gnome-pilot directory
in the .gnome directory to see if it would help, but I was getting the
same results.

> > gpilotd-Message: Performing Slow Synchronization 
> > GLib-ERROR **: could not allocate 825439550 bytes
> > aborting...
> > Aborted (core dumped)
> 
> Dude, thats a lot of memory. Could you "gdb `which gpilotd` core", type
> where and mail me the output ? I'd like to see which malloc caused this.
> 

[ken@hobbes ken]$ gdb `which gpilotd` core
GNU gdb 4.17.0.11 with Linux support
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for
details.
This GDB was configured as "i386-redhat-linux"...
warning: core file may not match specified executable file.
Core was generated by `gpilotd-control-applet'.
Program terminated with signal 6, Aborted.
#0  0x404df111 in ?? ()
(gdb) where
#0  0x404df111 in ?? ()
#1  0x404e0447 in ?? ()
#2  0x400a32d3 in ?? ()
#3  0x400a3396 in ?? ()
#4  0x804ce61 in ?? ()
#5  0x404d8cb3 in ?? ()
(gdb) 


I also tried this with `where gpilotd-control-applet` to see if it made
any more sense:

warning: core file may not match specified executable file.
Core was generated by `gpilotd-control-applet'.
Program terminated with signal 6, Aborted.
Reading symbols from /usr/lib/libgpilotd.so.0...done.
Reading symbols from /usr/lib/libgnome.so.32...done.
Reading symbols from /usr/lib/libgnomesupport.so.0...done.
Reading symbols from /usr/lib/libesd.so.0...done.
Reading symbols from /usr/lib/libaudiofile.so.0...done.
Reading symbols from /lib/libm.so.6...done.
Reading symbols from /lib/libdb.so.2...done.
Reading symbols from /usr/lib/libglib-1.2.so.0...done.
Reading symbols from /lib/libdl.so.2...done.
Reading symbols from /lib/libcrypt.so.1...done.
Reading symbols from /usr/lib/libcapplet.so.0...done.
Reading symbols from /usr/lib/libgnomeui.so.32...done.
Reading symbols from /usr/lib/libart_lgpl.so.2...done.
Reading symbols from /usr/lib/libgdk_imlib.so.1...done.
Reading symbols from /usr/X11R6/lib/libSM.so.6...done.
Reading symbols from /usr/X11R6/lib/libICE.so.6...done.
Reading symbols from /usr/lib/libgtk-1.2.so.0...done.
Reading symbols from /usr/lib/libgdk-1.2.so.0...done.
Reading symbols from /usr/lib/libgmodule-1.2.so.0...done.
Reading symbols from /usr/X11R6/lib/libXext.so.6...done.
Reading symbols from /usr/X11R6/lib/libX11.so.6...done.
Reading symbols from /usr/lib/libORBitCosNaming.so.0...done.
Reading symbols from /usr/lib/libORBit.so.0...done.
Reading symbols from /usr/lib/libIIOP.so.0...done.
Reading symbols from /usr/lib/libORBitutil.so.0...done.
Reading symbols from /lib/libnsl.so.1...done.
Reading symbols from /usr/lib/libgnorba.so.27...done.
Reading symbols from /usr/lib/libpisock.so.3...done.
Reading symbols from /lib/libc.so.6...done.
Reading symbols from /usr/lib/libz.so.1...done.
Reading symbols from /lib/ld-linux.so.2...done.
Reading symbols from /lib/libnss_files.so.2...done.
Reading symbols from /usr/lib/gconv/ISO8859-1.so...done.
Reading symbols from /usr/lib/gtk/themes/engines/libpixmap.so...done.
#0  0x404df111 in __kill ()
(gdb) where
#0  0x404df111 in __kill ()
#1  0x404ded66 in raise (sig=6) at ../sysdeps/posix/raise.c:27
#2  0x404e0447 in abort () at ../sysdeps/generic/abort.c:88
#3  0x400a32d3 in g_logv ()
#4  0x400a3396 in g_log ()
#5  0x804ce61 in main (argc=1, argv=0xbffffcc4) at
gpilotd-control-applet.c:892
#6  0x404d8cb3 in __libc_start_main (main=0x804ce20 <main>, argc=1,
    argv=0xbffffcc4, init=0x804a68c <_init>, fini=0x804e32c <_fini>,
    rtld_fini=0x4000a350 <_dl_fini>, stack_end=0xbffffcbc)
    at ../sysdeps/generic/libc-start.c:78
(gdb) 

> > The DateBook database on my Pilot is 142K, 2205 records, as reported by
> > the Info application on the Pilot. Also, it is not a true Pilot. I am beta
> > testing the TRGpro, a IIIx modified with 8MB of RAM, 3MB of flash and a CF
> > slot. None of that *should* affect the conduits, but who knows??
> 
> I can't say it won't have any effects, but if it's a PalmOS, it should
> work. And the alloc error is probably during reading the local records,
> doubt it is related to your FrankenPilot, but I need to see the stack
> trace.
> 

FrankenPilot?? I wouldn't go *quite* that far :)

Let me know if you need anything else from me.

Ken

-- 
><>   Ken Scott   kscott@pcisys.net   http://www.pcisys.net/~kscott   
                                                                      
              This is the day that the Lord has made;             
              I will rejoice and be glad in it!          -- Psalm 118:24