ok, to make sure the same compiler was
used for compiling octave and compiling my .oct file, I reinstalled octave
from the sources.
The used compiler was g++ 4.0.4. The
problem still occurs. I hope the attached bug report enables someone
to track down the problem.
Matthias
To: address@hidden
Cc: zomostud
Subject: iterator problem in .oct file
--------
Bug report for Octave 2.1.73 configured
for i486-pc-linux-gnu
Description:
-----------
* Please replace this item with
a detailed description of the
problem. Suggestions
or general comments are also welcome.
Repeat-By:
---------
* Please replace this item with
a description of the sequence of
events that causes the
problem to occur.
Fix:
---
* If possible, replace this item
with a description of how to
fix the problem (if you
don't have a fix for the problem, don't
include this section,
but please do submit your report anyway).
Configuration (please do not edit this
section):
-----------------------------------------------
* Please replace this item with
a detailed description of the
problem. Suggestions
or general comments are also welcome.
Repeat-By:
---------
* Please replace this item with
a description of the sequence of
events that causes the
problem to occur.
Fix:
---
* If possible, replace this item
with a description of how to
fix the problem (if you
don't have a fix for the problem, don't
include this section,
but please do submit your report anyway).
Configuration (please do not edit this
section):
-----------------------------------------------
> Am Dienstag, den 04.07.2006, 08:39 +0200 schrieb
> address@hidden:
> >
> > I am not very familiar with Linux. How can find out which compiler
> > version was used to compile the binary?
>
> If you have a precompiled package installed from your distribution,
> please tell the distribution.
>
> *Additionally*, run 'bug_report' from Octave's prompt. This will
> generate a report; depending on your system's setup, you can let the
> system mail the report automatically (which means it will be sent
to
> address@hidden, a mailing list) or you can copy the report into your
> favorite mail program and send the mail yourself.
>
> Please ensure that you copy *everything*.
>
> Thomas
>