Juliusz Chroboczek wrote:

Hi,

> 
> It looks like neither Denis nor I are able to reproduce it.  Any
> chance you could provide me with a backtrace ?
> 

I rebuilt polipo with debugging enabled and managed it to crash. However
today the crash occured after I reloaded the page from the link, I sent
in my bug report, and went to video.google.com.


> sudo gdb -c core.13-13.polipo-5363-6.1184315467 /usr/bin/polipo
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".

warning: Can't read pathname for load map: Input/output error.
Reading symbols from /lib/i686/cmov/libc.so.6...done.
Loaded symbols for /lib/i686/cmov/libc.so.6
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /lib/i686/cmov/libnss_files.so.2...done.
Loaded symbols for /lib/i686/cmov/libnss_files.so.2
Core was generated by `/usr/bin/polipo -c /etc/polipo/config
pidFile=/var/run/polipo/polipo.pid daemon'.
Program terminated with signal 6, Aborted.
#0  0xb7f97410 in __kernel_vsyscall ()
(gdb) bt
#0  0xb7f97410 in __kernel_vsyscall ()
#1  0xb7e5ad60 in raise () from /lib/i686/cmov/libc.so.6
#2  0xb7e5c5b1 in abort () from /lib/i686/cmov/libc.so.6
#3  0xb7e5442b in __assert_fail () from /lib/i686/cmov/libc.so.6
#4  0x0804d20f in dispose_chunk (chunk=0x6) at chunk.c:400
#5  0x0805ddae in httpServerHandler (status=65537, event=0x8089888,
srequest=0x8089898) at server.c:1748
#6  0x0804cb02 in do_scheduled_stream (status=-65537, event=0x8089888)
at io.c:284
#7  0x0804b3ba in pokeFdEventHandler (tevent=0x8087658) at event.c:569
#8  0x0804aa85 in runTimeEventQueue () at event.c:492
#9  0x0804b117 in eventLoop () at event.c:659
#10 0x080537c4 in main (argc=8, argv=0xbfaaf7c4) at main.c:165
(gdb)


Most of the polipo cores has the same backtrace as above.

But also there's one (from July 8th) with the following trace:

> sudo gdb -c core.13-13.polipo-2305-11.1183885370 /usr/bin/polipo
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".

warning: exec file is newer than core file.

warning: Can't read pathname for load map: Input/output error.
Reading symbols from /lib/i686/cmov/libc.so.6...done.
Loaded symbols for /lib/i686/cmov/libc.so.6
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /lib/i686/cmov/libnss_files.so.2...done.
Loaded symbols for /lib/i686/cmov/libnss_files.so.2
Core was generated by `/usr/bin/polipo -c /etc/polipo/config
pidFile=/var/run/polipo/polipo.pid daemon'.
Program terminated with signal 11, Segmentation fault.
#0  0x0805db60 in httpServerReplyHandler (status=-65540,
event=0x8086bf0, srequest=0x8086c00)
    at server.c:1788
1788    server.c: No such file or directory.
        in server.c
(gdb) bt
#0  0x0805db60 in httpServerReplyHandler (status=-65540,
event=0x8086bf0, srequest=0x8086c00)
    at server.c:1788
#1  0x0804cb02 in do_scheduled_stream (status=-65540, event=0x8086bf0)
at io.c:284
#2  0x0804b3ba in pokeFdEventHandler (tevent=0x80bacd8) at event.c:569
#3  0x0804aa85 in runTimeEventQueue () at event.c:492
#4  0x0804b117 in eventLoop () at event.c:659
#5  0x080537c4 in main (argc=8, argv=0xbfaaddc4) at main.c:165
(gdb)



Best Regards,
robert



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to