Hi Andy, I patched the debian source/debuild/dpkg -i with the 2 patches you mentioned and that were not in the debian ... but it still crash. this time the backtrace is larger, would it gives us more info?
I'll try to make a short example which 'mimics' what my app mainly do and try to make it crashing as well, if that 'works' I'll send it ... I will patch the git checkout for gtk > 2.18 and install from source in order to be able to do react in a 'quicker way' to suggestions: I am thinking that I should, with your help maybe, insert 'printf' 'everywhere until we can discover the source of my problem, what do toy think? Cheers, David ;; -- Le Sat, 03 Jul 2010 18:25:48 +0100, Andy Wingo <wi...@pobox.com> a écrit : > Hi, > > I had said: > > >> Can you check to see that the following patches are applied to the > >> debian package: > >> > >> 0ca1de9d89ed7b2899e49f273f27f810540a6508 > >> 3d11c93b290992b2c4d9eeef57c2a7a54f808783 > > These are git commits. > > You replied: > > On Fri 02 Jul 2010 17:32, David Pirotte <da...@altosw.be> writes: > > > I don't know, on the debian patch tracking system page for > > guile-gnome-platform, > > patches are listed by names. I don't see these [MD5sum?] numbers you > > mentioned, > > Chdir into gtk/ in your guile-gnome platform checkout, and do "gitk > REVNAME", and see if that patch is in debian. > > Regards, > > Andy
backtrace.txt.gz
Description: GNU Zip compressed data
