Package: awstats
Followup-For: Bug #706076
Both workarounds,
- Use NbOfLinesForCorruptedLog in awstats
- Adopt apache log configuration to hide such messages
have problematic side effects. I agree that the right solution is to:
(1) log invalid request names only on 400 ("Bad Request") response
Package: awstats
Followup-For: Bug #626185
Okay, so these are the exact steps how to reproduce this, using a
QEMU/KVM virtual machine running the latest Debian/Stable.
If you still can't reproduce this, please provide the Apache log line
you got instead, so I can analyze why you can't reproduce t
Package: awstats
Followup-For: Bug #626185
This issue is essentially the same as Bug #706076 from Apr 2013:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706076
Unfortunately, that one was closed prematurely, which is why this bug
still exists after 1.5 years. This is really a hassle to
Package: geeqie
Version: 1:1.2-1
Followup-For: Bug #762162
Dear Maintainer,
I have the same problem with geeqie.
The output of:
gdb -batch -n -ex run -ex bt -ex 'thread apply all bt full' --args geeqie
is:
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86
On Thu, Aug 10, 2006 at 05:59:53AM +0300, Panu Kalliokoski wrote:
> (Just to make sure: you do know it should probably be (let ((x 1)))?)
Of course I do. This was just a typo. :-)
Nevertheless, a program should never segfault, no matter how bad
the input was.
Greets,
Volker
--
Vol
Package: tinyscheme
Version: 1.37-3
Severity: important
To reproduce the bug, type this at the command line:
$ tinyscheme
TinyScheme 1.37
> (let (x 1))
Segmentation fault
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i
6 matches
Mail list logo
