Bug#691487: bsdmainutils: Segfault, easy to reproduce

2016-03-10 Thread Michael Meskes
> Well, whose fault would it be? My default is 1M stack size, and all
> other 
> programs seem to be fine with that...

Sorry, my message was confusing. This bug report was about a different
problem, the stack size one is still open. Besides, while I do agree
that memory handling should be changed, which would be a feature
request IMO, the segfault itself does not come from a bug in column.
Anyway, nitpicking, the code needs improvements. :)

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 Borussia! Força Barça! SF 49ers! Use Debian GNU/Linux, PostgreSQL



Bug#691487: bsdmainutils: Segfault, easy to reproduce

2016-03-10 Thread Philipp Marek
> > Well, it only got easier - just start it:
> > 
> > $ column
> > Speicherzugriffsfehler
> > ...
> 
> Let me guess, you've set ulimits on the process? column needs quite a bit of
> heap space for statically allocated buffers. Yes, it'd be nice if it was
> patched to use malloc, but the segfault is not really columns fault in this 
> case.
Yeah, right!

Thanks for the tip... somewhere between "ulimit -s4100" and "ulimit -s4200" 
there's the limit for being able to start column.


Well, whose fault would it be? My default is 1M stack size, and all other 
programs seem to be fine with that...


Thank you very much, and sorry for the noise.



Bug#691487: bsdmainutils: Segfault, easy to reproduce

2016-03-10 Thread Michael Meskes
On Thu, Mar 10, 2016 at 07:39:04AM +0100, Philipp Marek wrote:
> Well, it only got easier - just start it:
> 
> $ column
> Speicherzugriffsfehler
> ...

Let me guess, you've set ulimits on the process? column needs quite a bit of
heap space for statically allocated buffers. Yes, it'd be nice if it was
patched to use malloc, but the segfault is not really columns fault in this 
case.

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 Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL



Bug#691487: bsdmainutils: Segfault, easy to reproduce

2016-03-09 Thread Philipp Marek
Hi Michael,

> > When trying to use "column" I found an easy way to reproduce a segfault; 
> > I guess it's the same here, as both data files start with whitespace.
> > 
> > $ echo 'aa' | column
> > Segmentation fault
> > 
> > Ie. sending a  character as first character seems to cause the crash.
> 
> Not sure if this is the same problem or not, but again I cannot reproduce. Do
> you still see it? Any idea what might be different? I'm on up-to-date sid. Can
> you debug?
Well, it only got easier - just start it:

$ column
Speicherzugriffsfehler

$ gdb --args column
GNU gdb (Debian 7.10-1+b1) 7.10
...
Starting program: /usr/bin/column

Program received signal SIGSEGV, Segmentation fault.
0x00401919 in ?? ()
(gdb) bt
#0  0x00401919 in ?? ()
#1  0x00400f67 in ?? ()
#2  0x77a57870 in __libc_start_main (main=0x400d50, argc=0x1, 
argv=0x7fffdfa8, init=, fini=, 
rtld_fini=,
stack_end=0x7fffdf98) at libc-start.c:291
#3  0x00401001 in ?? ()

$ which column
/usr/bin/column
$ ls -la /usr/bin/column
-rwxr-xr-x 1 root root 14616 Nov 27 11:16 /usr/bin/column
$ sha1sum  /usr/bin/column
9d420d6114b0a1e55ca0c8ba3e694200d802a6fd  /usr/bin/column
$ md5sum  /usr/bin/column
e06e22651bc021be0effbccb494e8f5c  /usr/bin/column
$ dpkg-query -l  bsdmainutils
...
ii  bsdmainutils  9.0.6+b1amd64   collection of more utilities 
from FreeBSD
$ dpkg --verify bsdmainutils ; echo $?
0



Bug#691487: bsdmainutils: Segfault, easy to reproduce

2016-03-09 Thread Michael Meskes
On Thu, Jan 15, 2015 at 04:36:46PM +0100, Ph. Marek wrote:
> When trying to use "column" I found an easy way to reproduce a segfault; 
> I guess it's the same here, as both data files start with whitespace.
> 
> $ echo 'aa' | column
> Segmentation fault
> 
> Ie. sending a  character as first character seems to cause the crash.

Not sure if this is the same problem or not, but again I cannot reproduce. Do
you still see it? Any idea what might be different? I'm on up-to-date sid. Can
you debug?

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 Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL



Bug#691487: bsdmainutils: Segfault, easy to reproduce

2015-01-15 Thread Ph. Marek
Package: bsdmainutils
Version: 9.0.6
Followup-For: Bug #691487

When trying to use "column" I found an easy way to reproduce a segfault; 
I guess it's the same here, as both data files start with whitespace.

$ echo 'aa' | column
Segmentation fault

Ie. sending a  character as first character seems to cause the crash.



-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.17-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages bsdmainutils depends on:
ii  bsdutils 1:2.25.2-4
ii  debianutils  4.4+b1
ii  libc62.19-13
ii  libncurses5  5.9+20140913-1+b1
ii  libtinfo55.9+20140913-1+b1

bsdmainutils recommends no packages.

Versions of packages bsdmainutils suggests:
ii  cpp   4:4.9.2-1
pn  vacation  
ii  wamerican [wordlist]  7.1-1
ii  whois 5.2.3
ii  wngerman [wordlist]   20131206-5

-- no debconf information

-- 
: Ing. Philipp Marek
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com :

DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org