Hi, On Fri, Mar 21, 2014 at 07:36:02PM +0800, AkIrA YAnG wrote: > On Sat, Mar 15, 2014 at 11:43 PM, Juliusz Chroboczek wrote: > > > > Thanks for the report. Could I have a backtrace please? > > Here's the log which is taken with logLevel = 0xFF > "Read from server failed: Connection reset by peer" is where I disconnect > the parent proxy, then the CPU usage started surging, but there's no crash > or freezing. It seemed working normally when I turn the parent proxy back > on, but never let down the CPU usage.
Polipo's log is not as helpful as a backtrace. To get a backtrace of a running program, you can follow these instructions: http://www.dirac.org/linux/gdb/06-Debugging_A_Running_Process.php Basically, you should do something like: $ cd polipo; make $ ./polipo & # do whatever you need to trigger the busy loop, then: $ gdb ./polipo `pgrep polipo` # and then, in gbd's prompt: (gdb) backtrace full Copy-paste the result. You can also use "next" (several times) to carry on execution until you reach an interesting function (see link above for an example), and request a backtrace from there. Many thanks, -- Gabriel ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/polipo-users
