From help-request at octave dot org Sun Apr 16 09:41:32 2006 Subject: RE: Mkoctfile cygwin From: "Keshab Man Shrestha \(Dr\)" To: "Bill Denney" Cc: Date: Sun, 16 Apr 2006 22:40:13 +0800 Hi Bill, Thanks for the hints. I also installed Octave following the procedure posted by John Eaton ( on Wed Jan 14 13:37:15 2004). I can also compile the oregonator.cc inside the cygwin shell. Then I run octave and inside octave I entered "oregonator ([1.2.3].0)". This causes the octave to close (without any messave - may be it the message is quick for me to see) and I get back to the cygwin shell. May be there a way to capture the error message. I am new to cygwin and unix. I have been using the window version of octave. However, recently I tried got a program written in Matlab which I tried to run using octave with some necessary modifications. However, I realized the the program was very slow compared to matlab. I figured out the slow ness has to do with accessing individual element of a vector which is necessary in this case. Therefore, I though of writing dynamically linked function to do this part of the process. This is how I ended up trying to run mkoctfile. Since I do not like to use matlab, I have been spending quite a bit of time figuring out the process involved in writing dynamically linked function in C++. Any help on this is highly appreciated. Keshab -----Original Message----- From: Bill Denney [mailto:denney at seas dot upenn dot edu] Sent: Sunday, April 16, 2006 8:10 PM To: Keshab Man Shrestha (Dr) Cc: help at octave dot org Subject: Re: Mkoctfile cygwin On Sun, 16 Apr 2006, Keshab Man Shrestha (Dr) wrote: > I installed windows version of octave 2.1.73 (by downloading > octve-2-1.73-inst.exe). I could create the oregonator.oct file by > issuing the following commant inside octave > >>> system("mkoctfile oregonator.cc") > > I get > > ans = 0 > return. However, when I type "oregonator ([1,2,3],0)" inside octave. > It closes the octave window. > > Any help is highly appreciated. My guess would be that you're getting a segmentation fault when running your code and that the error goes by too quickly before the window closes. If you can find a way to run a shell and then run octave separately, then you should be able to find what the error is exactly when octave drops back to a shell. I don't run octave in windows with the same installer as you, so I don't know how to get to the shell, but I'm guessing that there is probably a batch file that starts it that you should be able to investigate to do it. Bill -- "Nothing says lovin' like somethin' from the oven." -- Joe Grange about cremation ------------------------------------------------------------- Octave is freely available under the terms of the GNU GPL. Octave's home on the web: http://www.octave.org How to fund new projects: http://www.octave.org/funding.html Subscription information: http://www.octave.org/archive.html -------------------------------------------------------------