On Wed, 2016-03-09 at 16:30 +0100, Michael Meskes wrote:
> I guess we can close it for now then. Should it re-appear feel free
> to re-open or open a new one.
Ok.
The invalid reads/writes are concerning though, if you want to try
finding crashes, the afl fuzzer is probably worth a try.
--
bye,
On Wed, 2016-03-09 at 11:09 +0100, Michael Meskes wrote:
> Do you still this segfault with the latest version? I cannot reproduce it at
> all and hope you don't see it either.
I can't reproduce it any longer, not sure why, but valgrind still
reports a bunch of invalid reads and invalid writes.
-
Do you still this segfault with the latest version? I cannot reproduce it at
all and hope you don't see it either.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Bo
On Thu, 2013-01-03 at 14:05 +0100, Michael Meskes wrote:
> Like this?
>
> michael@feivel:~$ export MALLOC_CHECK_=2
> michael@feivel:~$ export MALLOC_PERTURB_=$(($RANDOM % 255 + 1))
> michael@feivel:~$ column -ets, < foo > bar
> column: line too long
Correct.
> No segfault whatsoever.
H.
>
On Thu, Jan 03, 2013 at 08:41:59PM +0800, Paul Wise wrote:
> I still have the same problem on my wheezy system, the only difference
> to sid is that I have libc6 2.13-37 instead of 2.13-38 and an older
> version of valgrind.
>
> After upgrading libc6 the crash remains with the MALLOC_* variables s
I still have the same problem on my wheezy system, the only difference
to sid is that I have libc6 2.13-37 instead of 2.13-38 and an older
version of valgrind.
After upgrading libc6 the crash remains with the MALLOC_* variables set.
The invalid read is there with both new and old valgrinds and wi
On Fri, Oct 26, 2012 at 04:56:56PM +0800, Paul Wise wrote:
> Sorry for the noise, this only happens when I turn on malloc checks:
Do you still see the problem?
> valgrind also reports a problem:
On my up-to-date Sid system valgrind reports no problems whatsoever:
...
==31376== ERROR SUMMARY: 0 e
usertags 691487 + malloc
retitle 691487 column: memory allocation issue with a certain data and column
-ets,
thanks
> The attached text file and this command segfaults column:
>
> column -ets, < foo > bar
Sorry for the noise, this only happens when I turn on malloc checks:
export MALLOC_CHECK_
Package: bsdmainutils
Version: 9.0.3
Severity: normal
File: /usr/bin/column
The attached text file and this command segfaults column:
column -ets, < foo > bar
I note however that this command or different data does not:
column -ts, < foo > bar
-- System Information:
Debian Release: wheezy/sid
9 matches
Mail list logo
