|
From: | walt |
Subject: | [Pan-users] Re: Need some tips on debugging Pan |
Date: | Thu, 04 Feb 2010 12:26:33 -0800 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.3a1pre) Gecko/20100204 Thunderbird/3.2a1pre |
On 01/29/2010 02:23 PM, Steven Ellis wrote:
walt wrote:On 01/28/2010 06:31 PM, Steven Ellis wrote:Been a while since I've done this so I'm a bit out of practise. I'm getting a segfault loading one of my usenet groups with Pan 0.132 and Pan 0.133. I've just grabbed SVN trunk and done a quick compile with ./configure --enable-debug...Hi Steven, The svn repository is unfortunately way out of date now. Fortunately we have an actively maintained git repo from our Pan volunteer K. Haley: $git remote --verbose show origin git://github.com/lostcoder/pan2.git (fetch) origin git://github.com/lostcoder/pan2.git (push) The "integration" branch is the one K. Haley is hoping to be the next Pan release, so that would be the best branch to file bug reports against. Do you know how to use git? (Light-years ahead of svn.)Thanks Tried doing a git clone, problem is I use Pan on Centos 5.4 and so I don't have GLIB - version>= 2.14.0 Right now I'm just after some tips on gdb debugging pan so I can work out whats making the C call that is causing the crash.
Seems like some of the regulars here are hibernating for the winter. Your backtrace was very short. Did you try hitting 'Enter' a few times to see if there is more of the backtrace waiting to be printed out?
[Prev in Thread] | Current Thread | [Next in Thread] |