Subject: Re: Fwd: octave updated to 3.4.0-3. Please test (strcat error)
From: marco atzeri <[email-masked]>
To: "A.R. Burgers" <[email-masked]>
Cc: [email-masked]
Date: Fri, 1 Apr 2011 04:22:38 +0200
List-Id: <cygwin.cygwin.com>

On Thu, Mar 31, 2011 at 11:25 PM, A.R. Burgers  wrote:
> Op 31-3-2011 22:44, marco atzeri schreef:
>>
>> On Thu, Mar 31, 2011 at 10:21 PM, A.R. Burgers  wrote:
>>>
>>> LS,
>>>
>>> with the current octave, I get this octave strcat
>>> error on plot, both with xterm and the dumb terminal.
>>> Same error on two different windows XP systems.
>>> Same error with libstdc++6 and libgfortran3 from cygwin-ports gcc 4.5.2-2
>>>
>>> Teun
>>>
>>> $ octave
>>> GNU Octave, version 3.4.0
>>> Copyright (C) 2011 John W. Eaton and others.
>>>
>>> [snip]
>>>
>>> octave:1>  t=(0:0.1:2*pi);
>>> octave:2>  plot(t,sin(t))
>>> error: Invalid call to strcat.  Correct usage is:
>>>
>>>  -- Function File:  strcat (S1, S2, ...)
>>>
>>> error: called from:
>>> error:   /usr/share/octave/3.4.0/m/help/print_usage.m at line 87, column
>>> 5
>>> error:   /usr/share/octave/3.4.0/m/strings/strcat.m at line 92, column 5
>>> error:   /usr/share/octave/3.4.0/m/plot/__gnuplot_get_var__.m at line
>>> 113,
>>> column 11
>>> error:   /usr/share/octave/3.4.0/m/plot/__go_draw_axes__.m at line 40,
>>> column 18
>>> error:   /usr/share/octave/3.4.0/m/plot/__go_draw_figure__.m at line 167,
>>> column 19
>>> error:   /usr/share/octave/3.4.0/m/plot/__gnuplot_drawnow__.m at line 86,
>>> column 5
>>> octave:3>  quit
>>>
>>> BURGERS@P4949 ~
>>> $ echo $TERM $DISPLAY
>>> xterm :0
>>>
>>> BURGERS@P4949 ~
>>> $ cygcheck -c octave liblapack0 cygwin libqrupdate0 libgfortran3
>>> libstdc++
>>> gnuplot
>>> Cygwin Package Information
>>> Package              Version        Status
>>> cygwin               1.7.9-1        OK
>>> gnuplot              4.4.0-1        OK
>>> libgfortran3         4.3.4-4        OK
>>> liblapack0           3.2.2-2        OK
>>> libqrupdate0         1.1.1-1        OK
>>> octave               3.4.0-3        OK
>>>
>> could you just check if reversing to cygwin  1.7.8-1 solve the problem ?
>>
>> I also noted the same problem this morning, but it was puzzling and
>> NOT really repetitive.
>
> Your hunch was right, downgrading to 1.7.8-1 solves it
>
> Teun
>

it seems caused by a change between cygwin snapshots 20110308 and 20110309

Corinna, gcf
Have we catch a fhandler / pipe special case ?

Marco

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple