On Mon, Mar 26, 2012 at 11:11:47PM +0200, Vincent Lefevre wrote:
Something more complex, as
echo | gnuplot -
does not crash.
FYI,
$ echo foo | valgrind gnuplot -
==11357== Memcheck, a memory error detector
...
A null pointer dereference?
So, there seems to be a problem with
Vincent, are you affected with the bug #665832?
Thanks.
Anton
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On 2012-03-28 20:33:57 +0200, Anton Gladky wrote:
Vincent, are you affected with the bug #665832?
No (FYI, my machine is an x86_64).
--
Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/
100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/
Work: CR INRIA -
On Sat, Mar 24, 2012 at 04:07:12AM +0100, Vincent Lefevre wrote:
Package: gnuplot
Version: 4.6.0-1
Severity: important
Using stdin (whether the command makes sense or not), which is the
common way to call gnuplot from a script, makes gnuplot crash. For
instance:
$ echo foo | gnuplot -
Hi Agustin,
On 2012-03-26 18:10:02 +0200, Agustin Martin wrote:
In i386
$ echo foo | gnuplot
gnuplot foo
^
line 0: invalid command
However this form is not officially supported: from the gnuplot
man page:
If file names are given on the command line, gnuplot
On 2012-03-26 22:52:01 +0200, Vincent Lefevre wrote:
It was supported in the past, at least up to 4.4 (by convention, '-'
generally means stdin in command arguments when a filename is expected,
even though this is not always documented). However I've just noticed
that there's no such problem
Package: gnuplot
Version: 4.6.0-1
Severity: important
Using stdin (whether the command makes sense or not), which is the
common way to call gnuplot from a script, makes gnuplot crash. For
instance:
$ echo foo | gnuplot -
Segmentation fault (core dumped)
-- System Information:
Debian Release:
7 matches
Mail list logo
