[ Apologies for the delay in looking into this. Life's been hectic beyond belief lately... ]
On Tue, Sep 27, 2005 at 09:58:10PM +0200, Major A wrote: >Steve, > >> Hmmm. The easiest way to do that might be to write a wrapper shell >> script that will do "ulimit -c unlimited" to turn on core dumps, then >> calls the normal cvs binary. If you can try that and mail me a core >> dump, I might be able to debug it here. > >Done that. I'm sending you the core file, please don't upload it to >the bugs database or elsewhere because it may contain sensitive >information (I don't want my cvs files to become public). Of course. From looking into that core, the stack is _huge_ and looks very corrupt. Martin Pitt says that Ubuntu have seen a similar problem, and it appears to be compiler-related. Checking the build log at http://amd64.ftbfs.de/fetch.php?&pkg=cvs&ver=1%3A1.12.9-15&arch=amd64&stamp=1125622007&file=log&as=raw it seems that your build of cvs on amd64 was built using gcc-4.0 version 4.0.1-6. In the archive currently is 4.0.2-2. _Hopefully_ simply rebuilding with a new compiler may fix the problem. Can you please try the (unofficial) release of cvs I've just built at http://www.einval.com/debian/cvs/cvs_1.12.9-15_unofficial_amd64.deb and let me know if it fixes your problem? -- Steve McIntyre, Cambridge, UK. [EMAIL PROTECTED] Is there anybody out there?
signature.asc
Description: Digital signature
