Package: lockfile-progs
Version: 0.1.13
Severity: important
Tags: patch
Whenever I try to use mail-lock or mail-unlock the commands print the
usage information. E.g.
$ mail-lock
usage: mail-lock [--use-pid] [--retry retry-count]
This issue only appeared after upgrading to squeeze and it also exi
Peter Karlsson wrote:
> >Hmmm, I tried to create messages with 16000, 17000 and 32000 characters in
> >a line, but this didn't trigger the bug. :/
> I was just able to create a message that would crash uqwk. Unfortunately,
> it was the version with my proposed fix for the bug, so I will have to
Hi Peter,
Peter Karlsson wrote:
> >Another measure I could think of, would be to make buf a dynamically
> >allocated array and malloc() BUFLEN bytes on program startup. I have not
> >checked the code whether this might be feasible.
> Yes, that is the solution I am looking into. It would be easie
Hi Peter,
Peter Karlsson wrote:
> >By replacing fgets() in this location, I could make uqwk work, but as
> >there are plenty of other Fgets()s in the code, this seems to require
> >further analysis.
> Yes, there seems to be a bit of a misunderstanding between these files. Do
> you have an example
Package: uqwk-spool
Version: 2.21-12
Severity: important
When running
# uqwk +m -H
I something get the following error (if there is some pattern in at
least one mail -- mostly spam):
*** glibc detected *** realloc(): invalid pointer: 0x08057520 ***
Aborted
By reading the source, I found that
5 matches
Mail list logo
