[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #33670] bug in strfind
From: |
Thomas Smed |
Subject: |
[Octave-bug-tracker] [bug #33670] bug in strfind |
Date: |
Wed, 29 Jun 2011 13:39:27 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110420 SUSE/3.6.17-0.2.1 Firefox/3.6.17 |
URL:
<http://savannah.gnu.org/bugs/?33670>
Summary: bug in strfind
Project: GNU Octave
Submitted by: thomassmed
Submitted on: Wed 29 Jun 2011 01:39:26 PM GMT
Category: None
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Crash
Status: None
Assigned to: None
Originator Name: Thomas Smed
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: 3.4.0
Operating System: GNU/Linux
_______________________________________________________
Details:
I use strfind to navigate in a file created by FORTRAN, the file contains a
mix of charaters, float and integers (big endian is used).
I found this error which I could simplify down to:
octave:1> test_str=' PAR ';
octave:2> label='PAR ';
octave:3> strfind(test_str,label)
ans = 2
octave:4> test_str(end)=255;
octave:5> strfind(test_str,label)
Now octave freezes and a triple ctrl-C is all that can take me out of the
deadlock.
Thus, when there is 255 in one byte, strfind collapses.
Another akward detail is that after I had been working a while
with something else in one session of octave, and wanted to demonstrate the
error to a colleague, the error had disappeared.
I have however not been able to recreate how the make the error disappear. If
you try the above lines directly when getting in to octave, the error will be
present.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?33670>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Octave-bug-tracker] [bug #33670] bug in strfind,
Thomas Smed <=