Martin,

I can work on that for us, Maybe if SUV can get me that info please I can right this out in a short time. If that work I will begin and show links to the view before uploading to the staging site.

Regards, Leo Jackson

________________________________ From: Martin Owens <doctormo@...400...> To: Inkscape Devel List inkscape-devel@lists.sourceforge.net Sent: Monday, September 23, 2013 11:49 AM Subject: [Inkscape-devel] Website: Debugging Page

Hey Devs,

I'm calling on those who know to help write out new debugging page here:

http://staging.inkscape.org/en/develop/debugging/

It needs to contain the information on the wiki here:

http://wiki.inkscape.org/wiki/index.php/Debugging_Inkscape

As well as information about logging (enabling, different log options), using gdb and links to where to get gdb help or a gui for gdb. Anything extra such as compile flags to improve logging and using cout or g_warning or g_info statements in code and when it's good to use them.

I'd also like something about how to use the multiple packages we have in the trunk ppa system to narrow down a problem. I think SUV has this magic already, allowing other bug hunters and devels to know how to set that up would be very useful.

Best Regards, Martin Owens

------------------------------------------------------------------------------ LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clk... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

On 2013-09-23 17:49 +0200, Martin Owens wrote:

I'd also like something about how to use the multiple packages we have in the trunk ppa system to narrow down a problem. I think SUV has this magic already, allowing other bug hunters and devels to know how to set that up would be very useful.

Not really, MARTIN. I use a not-so proper (aka proprietary) OS as main platform, and have no magic at hand to share on how to use multiple packages from the inkscape-trunk PPA on Ubuntu for bug triage.

My own usage of PPAs is limited to keeping inkscape-trunk more or less up-to-date in two Ubuntu VMs (12.04, 13.04), but in those VMs I never downgrade or test with multiple versions other than the current latest one available from the PPA.

Archived builds mentioned in my comments in the bug tracker are all locally compiled and - per branch - installed into a custom $PREFIX. For the most part these builds are done on OS X, and and only a few in a Ubuntu 12.10 VM. My "archiving" method is very crude, and limited to the main inkscape binary (caveat: within the same prefix, the shared resources are always those from HEAD, even if I run an "archived" binary). Basic step is to rename the installed binary before pulling/updating:

$ mv $PREFIX/bin/inkscape{,-`bzr revno`} $ bzr pull $ # out-of-src build [1] $ (cd build; make && make install)

I'm sure there are better and more sophisticated ways to maintain a local archive of older builds - for me, it serves its purpose.

Regards, V

[1] http://article.gmane.org/gmane.comp.graphics.inkscape.devel/37448