Re: trying to track down memo-file conduit bug

[Jason 'vanRijn' Kasper <vR movingparts net>]

I'm not sure I understand.  Are you saying that you're running the below 
versions of software and you _are_ able to sync memo_file or, that when you 
rolled glib back to 2.2.1, other things got fixed, but memo_file is still 
broken?

On Thursday 31 July 2003 09:12 am, Hought, Todd wrote:
> I'm not much of a coder, but this may not necessarily be related to
> gpilotd or the applet, qas I am running mostly new versions of
> everything needed to sync, and recently watched as everything just
> 'stopped working' after a system software upgrade. This was not through
> any defect in gnome-pilot, the conduits, or gpilot. I soon found out
> that something had gone wrong with glib, version 2.2.2, and rolling my
> installation of glib back to version 2.2.1 caused everything to be nice
> and happy again.
>
> And just to get it on record:
> Gnome-pilot-conduits - version 2.0.9
> pilot-link - 0.11.7
> gnome-pilot - 2.0.9
> glib - version 2.2.1
> evolution - 1.4.3
> Gentoo GNU/Linux 1.4 with kernel 2.4.20
> and I have a palm M500 usb.
>
> In fact, going though my system to get version numbers, I stand behind
> my theory a little bit more, since I'm using software that's one version
> back, and I cannot sync the memo-file conduit, either.
>
> Hope this helps, and keep up the good work, Pilot Guys. :-)
>
> -T
>
> On Wed, 2003-07-30 at 19:33, Jason 'vanRijn' Kasper wrote:
> > so, I spent some time last night trying to track down the memo-file
> > conduit bug and I'm confused.
> >
> > I've diffed the memo_file directory between 0.10 and 2.0.10 and there's
> > VERY little code that has changed between the two versions--certainly
> > nothing that looks fishy.
> >
> > Also, I've added debug statements to track down where gpilotd is dying,
> > exactly, and I have narrowed it down to one line of code, and now I'm
> > even more confused.  The memo_file conduit seems like it doesn't have
> > any problems finishing its task.  The bug seems to be in gpilotd(?)....
> >
> > Specifically, when I do a regular synchronize between my palm and
> > gpilotd, with ONLY the memo_file conduit enabled, the last thing I see
> > gpilotd print out is this  "Performing Fast Synchronization", which is
> > at line 1598 or so of gnome-pilot-conduit-standard-abs.c (from
> > gnome-pilot-2.0.10/gpilotd/).  The problem is that gpilotd never makes
> > it through the next line of code.  If I add a g_message after the call
> > to dlp_ReadNextModifiedRec, it never gets printed out.  I'm not familiar
> > with this method, and apparently, it's not documented(?) from what I saw
> > on the 'net.  And I believe it comes from pilot-link itself(??).
> >
> > What I don't understand is where to go from here.  Because of all the
> > interdependencies with bonobo/etc., this is REALLY hard to track down.
> > If I start gpilotd in gdb and let it crash, the backtrace is a
> > completely useless 1-liner with no reference points.
> >
> > 	while (dlp_ReadNextModifiedRec (handle, db,
> > 					remote.record,
> > 					&remote.ID,
> > 					&index,
> > 					&remote.length,
> > 					&remote.attr,
> > 					&remote.category) >= 0) {
> > 	  g_message("got here gpilotd - a");
> >
> > To quote a certain doctor...  "somebody throw me a frickin' bone
> > here"???  =:D
>
> _______________________________________________
> gnome-pilot-list mailing list
> gnome-pilot-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-pilot-list

-- 

,-----------------------------------------------------------------//
| Jason 'vanRijn' Kasper ::  Numbers 6:22-26 
 `
 | All brontosauruses are thin at one end, much MUCH thicker 
 | in the middle, and then thin again at the far end.  That is 
 | the theory that I have and which is mine, and what it is too.  
 ,
| bash$ :(){ :|:&};:
`----------------------//

__________________________________________________________________________
Disclaimer: This e-mail message is intended only for the personal use of 
the recipient(s) named above.  If you are not an intended recipient, you 
may not review, copy or distribute this message. If you have received this
communication in error, please notify us immediately by e-mail and delete 
the original message.
This e-mail expresses views only of the sender, which are not to be 
attributed to Rite Aid Corporation and may not be copied or distributed 
without this statement.