On 2012-01-06 08:04 +0100, Raphael Geissert wrote:
On Thursday 05 January 2012 15:36:47 Raphael Geissert wrote:
Apparently nobody had run valgrind on the collector for a long time and
there are lots of bugs, but those have been there for a long time. Will
probably address them by tomorrow and
tag 654678 pending
thanks
On Friday 06 January 2012 03:51:29 Sven Joachim wrote:
How should I proceed to obtain a backtrace? Running readahead-collector
manually does not seem to do anything, and the manpage is rather terse.
Right, I could extend the manpage a bit. The collector is not really
Hi,
On Thursday 05 January 2012 01:07:57 Sven Joachim wrote:
I have been seeing these segfaults since the upgrade to 2:1.5.6-2,
IIRC. At least, there are several other occurrences of them in
/var/log/messages*, while an entry from December 10 (when I still head
2:1.5.6-1 installed) does not
On Thursday 05 January 2012 15:36:47 Raphael Geissert wrote:
Apparently nobody had run valgrind on the collector for a long time and
there are lots of bugs, but those have been there for a long time. Will
probably address them by tomorrow and post a patch, so that if you have no
luck with the
Package: readahead-fedora
Version: 2:1.5.6-3
Severity: normal
I noticed these messages in the syslog:
,
| Jan 5 07:49:09 turtle kernel: [ 27.716211] type=1305
audit(1325746149.941:6): auid=4294967295 ses=4294967295 op=remove rule
key=(null) list=4 res=1
| Jan 5 07:49:09 turtle kernel:
5 matches
Mail list logo
