[changeset] uninitialized value bug in strncmp
Jaroslav Hajek
highegg at gmail.com
Mon Jan 12 01:54:30 CST 2009
On Mon, Jan 5, 2009 at 11:02 AM, Thorsten Meyer <thorsten.meyier at gmx.de> wrote:
> Jaroslav Hajek wrote:
>
> On Thu, Jan 1, 2009 at 1:20 PM, Thorsten Meyer <thorsten.meyier at gmx.de>
> wrote:
>
>
> Hi,
>
> here is a patch (against mercurial) for the following bug in strncmp:
>
> comparing a string with a cell array, the return value for non-character
> cells is random:
>
> octave:1> strncmp("abc", {"abcd", 10}, 2)
> ans =
>
> 1 164
>
> octave:2>
> octave:2> strncmp("abc", {"abcd", 10}, 2)
> ans =
>
> 1 191
>
> octave:3> strncmp("abc", {"abcd", 10}, 2)
> ans =
>
> 1 184
>
> octave:4> strncmp("abc", {"abcd", 10}, 2)
> ans =
>
> 1 138
>
> The reason is that in this particular case, the output value is left
> uninitialized.
>
> regards
>
> Thorsten
>
> _______________________________________________
> Bug-octave mailing list
> Bug-octave at octave.org
> https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave
>
>
>
> Attachment missing?
>
>
> Yes, sorry, here it is.
>
>
>
It's OK. Since you have now access to Savannah, please go ahead and
push it. Let me know if you have problems.
cheers
--
RNDr. Jaroslav Hajek
computing expert
Aeronautical Research and Test Institute (VZLU)
Prague, Czech Republic
url: www.highegg.matfyz.cz
More information about the Bug-octave
mailing list