Bug report

[..::BAS::..]

Hello,

After installing Octave on Windows 2000 Pro SP4, I immediately had 2 (or 3)
problems:

1th attempt to run Octave: Missing MSVCP71.DLL. I fixed this by placing this
file (version 7.10.3077.0) in my System32 directory.

2th attempt: Octave crashed immediately. See attached Inspector IIXII
logfile for details.

3th attempt: An error message saying that Octave possibly was still running
(not the case). See attached screenshot.

As requested, hereby the following info:


   - The version of Octave. You can get this by noting the version number
   that is printed when Octave starts, or running it with the -v option.
   3.0.0 (Windows)
   - A complete input file that will reproduce the bug. A single
   statement may not be enough of an example--the bug might depend on other
   details that are missing from the single statement where the error finally
   occurs. Non applicable
   - The command arguments you gave Octave to execute that example and
   observe the bug. To guarantee you won't omit something important, list all
   the options. If we were to try to guess the arguments, we would probably
   guess wrong and then we would not encounter the bug. Non applicable
   - The type of machine you are using, and the operating system name and
   version number. Intel 450 Hrz PC with 64 MB RAM (I know, a old machine
   ;-) with Windows 2000 Pro, SP 4
   - The command-line arguments you gave to the configure command when
   you installed the interpreter. Non applicable
   - A complete list of any modifications you have made to the
   interpreter source. Be precise about these changes--show a context diff for
   them. Non applicable
   - Details of any other deviations from the standard procedure for
   installing Octave. Installed on a local directory different from
   c:\program files.
   - A description of what behavior you observe that you believe is
   incorrect. For example, "The interpreter gets a fatal signal," or, "The
   output produced at line 208 is incorrect." Of course, if the bug is that the
   interpreter gets a fatal signal, then one can't miss it. But if the bug is
   incorrect output, we might not notice unless it is glaringly wrong. Even if
   the problem you experience is a fatal signal, you should still say so
   explicitly. Suppose something strange is going on, such as, your copy of the
   interpreter is out of synch, or you have encountered a bug in the C library
   on your system. Your copy might crash and the copy here would not. If you
   said to expect a crash, then when the interpreter here fails to crash, we
   would know that the bug was not happening. If you don't say to expect a
   crash, then we would not know whether the bug was happening. We would not be
   able to draw any conclusion from our observations. Often the observed
   symptom is incorrect output when your program is run. Unfortunately, this is
   not enough information unless the program is short and simple. It is very
   helpful if you can include an explanation of the expected output, and why
   the actual output is incorrect. Octave crashed
   - If you wish to suggest changes to the Octave source, send them as
   context diffs. If you even discuss something in the Octave source, refer to
   it by context, not by line number, because the line numbers in the
   development sources probably won't match those in your sources. Non
   applicable

Hope this helps!

 - Bas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www.cae.wisc.edu/pipermail/bug-octave/attachments/20080320/e61f15ae/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: shot_20080320170258-583.png
Type: image/png
Size: 1954 bytes
Desc: not available
Url : https://www.cae.wisc.edu/pipermail/bug-octave/attachments/20080320/e61f15ae/attachment-0001.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: crash20080320170213.rar
Type: application/octet-stream
Size: 24405 bytes
Desc: not available
Url : https://www.cae.wisc.edu/pipermail/bug-octave/attachments/20080320/e61f15ae/attachment-0001.obj