On Tue, Feb 24, 2009 at 08:15:29AM +0100, Didrik Pinte wrote: > Package: proj > Version: 4.6.1-1 > Severity: normal > > > Hi, > > I do not know if it is the right place to report this problem but ... > > Thus, since last glibc update (glibc (2.9-2) unstable; urgency=low), Thuban > seems to have problem using extension linked to proj. > > See the stacktrace here below : > > *** glibc detected *** /usr/bin/python: free(): invalid pointer: > 0x0000000005214e20 *** > ======= Backtrace: ========= > /lib/libc.so.6[0x7f5d889651b8] > /lib/libc.so.6(cfree+0x76)[0x7f5d88966cf6] > /usr/lib/libproj.so.0(pj_free+0x28)[0x7f5d74b3a378] > /home/did/projets/python/thuban/current/thuban/Thuban/../Lib/Projectionc.so(delete_Projection+0x17)[0x7f5d7490a607] > /home/did/projets/python/thuban/current/thuban/Thuban/../Lib/Projectionc.so[0x7f5d7490a67a] > /usr/bin/python(PyEval_EvalFrameEx+0x4e95)[0x4911d5] > > I have rebuilded Thuban from scratch to be sure it was not related to old > binaries of extensions but the problem is still there. > > I can provide more info if needed. > > Didrik
Good catch. I would presume that it is a nice swig-related issue due to the new glibc. Did you try to rebuild swig stuff from scratch? What arch are you using? -- Francesco P. Lovergine _______________________________________________ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-devel
