Segfault with bad argument

[GoogleCodeExporter]

What is the expected output? What do you see instead?

When used with improper argument value it segfaults. E.g. wbar -p or wbar -d.

What version of the product are you using? On what operating system?

Last version from source (1.3.3)
compiled under Debian sid with kernel 2.6.25 on a P4 with gcc 4.2.4
(here's the -v output)
Target: i486-linux-gnu
Configured with: ../src/configure -v
--enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared
--with-system-zlib --libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --enable-nls
--with-gxx-include-dir=/usr/include/c++/4.2 --program-suffix=-4.2
--enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc
--enable-mpfr --disable-libmudflap --enable-targets=all
--enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu
--target=i486-linux-gnu
Thread model: posix
gcc version 4.2.4 20080512 (prerelease) (Debian 4.2.3-6)

Please provide any additional information below.

Original issue reported on code.google.com by systemfa...@gmail.com on 21 May 2008 at 5:17

[GoogleCodeExporter]

I had some luck changing from abbreviated commands to longer ones.
Eg.

wbar -j 0 -p top -nanim 3 -z 2.0 -above-desk -bpress

segfaulted, but 

wbar -jumpf 0 -pos top -nanim 3 -zoomf 2.0 -above-desk -bpress'

worked.

Original comment by joachim....@gmail.com on 29 Aug 2009 at 3:41

[GoogleCodeExporter]

Original comment by yadick...@gmail.com on 5 Jan 2011 at 8:50

• Changed state: Accepted

[GoogleCodeExporter]

does not apply, see README for compiler and help of wbar
thanks

Original comment by yadick...@gmail.com on 14 Jan 2011 at 3:17

• Changed state: Invalid