[changeset] uninitialized value bug in strncmp

Thorsten Meyer thorsten.meyier at gmx.de
Mon Jan 5 04:02:56 CST 2009


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.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www-old.cae.wisc.edu/pipermail/bug-octave/attachments/20090105/a379d594/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fix_strncmp.patch
Type: text/x-patch
Size: 1150 bytes
Desc: not available
Url : https://www-old.cae.wisc.edu/pipermail/bug-octave/attachments/20090105/a379d594/attachment.bin 


More information about the Bug-octave mailing list