On Fri, Mar 14, 2014 at 07:21:39PM +0100, Aleksandar Kuktin wrote: > >On Fri, 14 Mar 2014 17:40:24 +0100 > >Aleksandar Kuktin <akuk...@gmail.com> wrote: > > > The kernel message is thus: > > segfault at bf3e0ffc ip 080571fd sp bf3e1000 error 6 in > > polipo[8048000+2a000] > > Through a little experimentation, I have been able to discern that this > mode of failure happens when a program exceeds its stack resource > allocation. Basically, when the growing stack smashes its lower > boundary. > > That can happen either as a consequence of an off-the-rails infinite > recursion, otherwise excessive recursion, or possibly as a > consequence of the stack pointer being doctored. > > As this crash is possibly a consequence of an infinite function > recursion, it may or may not be related to the crash reported by > Richard Z in "first crash with polipo-20140107". With that in mind, > it's important that my system does not logrotate, and it also doesn't > have systemd (assuming /bin/systemctl is part of systemd).
I have meanwhile got a few more of those crashes, mine happen always in offline mode. It was trigered by logrotate because polipo was accidentally put into offline mode for logrotation For some reason offline browsing is extremely fragile here, aside of these crashes I also get very frequent symptoms of hanging - only restarting polipo will cure those. Very solid in online mode, no difficulties detected so far. Richard --- Name and OpenPGP keys available from pgp key servers ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech _______________________________________________ Polipo-users mailing list Polipo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/polipo-users
