[Lilug-dev-sig] Best way to troubleshoot

Rob Wilkens robwilkens at gmail.com
Fri Dec 25 06:45:23 PST 2009


debuild doesn't actually upload my changes anywhere, does it?  I just
added some printfs for debugging and rebuilt and during the debuild it
said:

 dpkg-genchanges: including full source code in upload
dpkg-buildpackage: full upload (original source is included)

My intention was not to have this debug version sent to anyone else
(at least until a problem has been solved).

BTW As long as i'm writing, I'll share the problem seems to "move" in
that i've seen at least three different stack traces, but always seems
to ultimately fail when it's in camel_pop3_engine_command_free() ,,
which is a simple routine that frees the memory associated with a pop3
command sent to the server.  It also always seems to happen on my
robwilkens at optonline.net account from what i can see, but it's
possible that just gets processed first.

>   - when you're ready to try evolution after you've modified the
>     source, build a package you can install via "debuild -us -uc"
>     within source directory (it's part of the "devscripts" package)



More information about the Lilug-dev-sig mailing list