Tinyproxy segfault at logrotate
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tinyproxy (Debian) |
Fix Released
|
Unknown
|
|||
tinyproxy (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: tinyproxy
Description: Ubuntu 10.04.1 LTS
Release: 10.04
Package: tinyproxy 1.8.1-3
Tinyproxy segfaults everyday at the log rotation time.
There is the syslog trace:
Aug 27 06:53:14 gwtex kernel: [714289.697157] __ratelimit: 6 callbacks suppressed
Aug 27 06:53:14 gwtex kernel: [714289.697163] tinyproxy[9556]: segfault at 0 ip 00007f1f8b91c53a sp 00007fff9b6ac4b8 error 4 in libc-2.
Aug 27 06:53:14 gwtex kernel: [714289.706658] tinyproxy[9555]: segfault at 0 ip 00007f1f8b91c53a sp 00007fff9b6ac4b8 error 4 in libc-2.
Aug 27 06:53:14 gwtex kernel: [714289.716107] tinyproxy[9553]: segfault at 0 ip 00007f1f8b91c53a sp 00007fff9b6ac4b8 error 4 in libc-2.
Aug 27 06:53:14 gwtex kernel: [714289.725047] tinyproxy[9554]: segfault at 0 ip 00007f1f8b91c53a sp 00007fff9b6ac4b8 error 4 in libc-2.
Aug 27 06:53:14 gwtex kernel: [714289.732658] tinyproxy[9558]: segfault at 0 ip 00007f1f8b91c53a sp 00007fff9b6ac4b8 error 4 in libc-2.
Aug 27 06:53:14 gwtex kernel: [714289.734861] tinyproxy[9561]: segfault at 0 ip 00007f1f8b91c53a sp 00007fff9b6ac4b8 error 4 in libc-2.
Aug 27 06:53:14 gwtex kernel: [714289.737191] tinyproxy[9560]: segfault at 0 ip 00007f1f8b91c53a sp 00007fff9b6ac4b8 error 4 in libc-2.
Aug 27 06:53:14 gwtex kernel: [714289.739771] tinyproxy[9562]: segfault at 0 ip 00007f1f8b91c53a sp 00007fff9b6ac4b8 error 4 in libc-2.
Aug 27 06:53:14 gwtex kernel: [714289.742725] tinyproxy[9559]: segfault at 0 ip 00007f1f8b91c53a sp 00007fff9b6ac4b8 error 4 in libc-2.
Aug 27 06:53:14 gwtex kernel: [714289.745879] tinyproxy[9552]: segfault at 0 ip 00007f1f8b91c53a sp 00007fff9b6ac998 error 4 in libc-2.
It seems that it is a known bug from a Debian package.
Changed in tinyproxy (Debian): | |
status: | Unknown → Fix Released |
Changed in tinyproxy (Ubuntu): | |
status: | Confirmed → Fix Released |
Status changed to 'Confirmed' because the bug affects multiple users.