|
View:
New views
8 Messages
—
Rating Filter:
Alert me
|
|
|
octave crash with repetitive 'clear functions'While playing with optiplux (optilux.sf.net) again, which is written for
octave and matlab, I ran into problems. I could reduce the problem to the following example. When running myscript.m, which calls myfun.m octave dies with a segmentation fault at the second 'clear functions'. kai@LxLap:~/hg-octave/octave> cat myscript.m clear functions myfun clear functions kai@LxLap:~/hg-octave/octave> cat myfun.m function myfun function f1 function f2 kai@LxLap:~/hg-octave/octave> ./run-octave --silent adding ssprop to path adding optilux to path octave:1> myscript panic: Segmentation fault -- stopping myself... attempting to save variables to `octave-core'... save to `octave-core' complete Speicherzugriffsfehler kai@LxLap:~/hg-octave/octave> I have observed this with a recent tip (yesterday), but not with the mingw octave3.2.2 binary. Can someone confirm this crash? Attached is a backtrace of the crash: octave:1> myscript Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb577f9e0 (LWP 5227)] 0x00000004 in ?? () (gdb) bt #0 0x00000004 in ?? () #1 0xb692345c in do_clear_functions (argv=@0xbfaafac0, argc=2, idx=2, exclusive=192) at variables.cc:1936 #2 0xb6927ca8 in Fclear (args=@0x83cd200) at variables.cc:2073 #3 0xb6a1c2c7 in octave_builtin::do_multi_index_op (this=0x8110ae0, nargout=0, args=@0x83cd200) at ov-builtin.cc:107 #4 0xb6a1b2db in octave_builtin::subsref (this=0x8110ae0, type=@0xbfaafe08, idx=@0xbfaafdfc, nargout=0) at ov-builtin.cc:55 #5 0xb69d4ec8 in octave_value::subsref (this=0xbfaafe1c, type=@0xbfaafe08, idx=@0xbfaafdfc, nargout=0) at ov.cc:1173 #6 0xb6b00dfb in tree_index_expression::rvalue (this=0x843acc0, nargout=0) at pt-idx.cc:398 #7 0xb6b017f4 in tree_index_expression::rvalue1 (this=0x843acc0, nargout=0) at pt-idx.cc:409 #8 0xb6af2c21 in tree_evaluator::visit_statement (this=0xb71612cc, stmt=@0x843d0b0) at pt-eval.cc:695 #9 0xb6b186bb in tree_statement::accept (this=0x843d0b0, tw=@0xb71612cc) at pt-stmt.cc:152 #10 0xb6af1e6b in tree_evaluator::visit_statement_list (this=0xb71612cc, lst=@0x8419200) at pt-eval.cc:731 #11 0xb6b186db in tree_statement_list::accept (this=0x8419200, tw=@0xb71612cc) at pt-stmt.cc:216 #12 0xb6a24606 in octave_user_script::do_multi_index_op (this=0x81d6d18, nargout=0, args=@0xbfab0048) at ov-usr-fcn.cc:137 _______________________________________________ Bug-octave mailing list Bug-octave@... https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave |
|
|
Re: octave crash with repetitive 'clear functions'-------- Original-Nachricht -------- > Datum: Thu, 22 Oct 2009 14:12:35 +0200 > Von: Kai Habel <kai.habel@...> > An: bug-octave@... > Betreff: octave crash with repetitive \'clear functions\' > While playing with optiplux (optilux.sf.net) again, which is written for > octave and matlab, I ran into problems. > > I could reduce the problem to the following example. When running > myscript.m, which calls myfun.m octave dies with a segmentation fault at > the second 'clear functions'. > > kai@LxLap:~/hg-octave/octave> cat myscript.m > clear functions > myfun > clear functions > kai@LxLap:~/hg-octave/octave> cat myfun.m > function myfun > function f1 > function f2 > kai@LxLap:~/hg-octave/octave> ./run-octave --silent > adding ssprop to path > adding optilux to path > octave:1> myscript > panic: Segmentation fault -- stopping myself... > attempting to save variables to `octave-core'... > save to `octave-core' complete > Speicherzugriffsfehler > kai@LxLap:~/hg-octave/octave> > > I have observed this with a recent tip (yesterday), but not with the > mingw octave3.2.2 binary. Can someone confirm this crash? > Nobody? I had the chance to test it on a second Opensuse system and still see the crash, so I suspect the problem is with octave and not with my local installation(s). To test, create two files: 1.myfun.m function myfun function f1 function f2 2. myscript.m clear functions myfun clear functions If I call myscript octave dies with a segmentation fault. Kai _______________________________________________ Bug-octave mailing list Bug-octave@... https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave |
|
|
Re: octave crash with repetitive 'clear functions'Hi Kai,
On Mon, Oct 26, 2009 at 09:09:54PM +0100, Kai Habel wrote: > > -------- Original-Nachricht -------- > > Datum: Thu, 22 Oct 2009 14:12:35 +0200 > > Von: Kai Habel <kai.habel@...> > > An: bug-octave@... > > Betreff: octave crash with repetitive \'clear functions\' > > > While playing with optiplux (optilux.sf.net) again, which is written for > > octave and matlab, I ran into problems. > > > > I could reduce the problem to the following example. When running > > myscript.m, which calls myfun.m octave dies with a segmentation fault at > > the second 'clear functions'. > > > > kai@LxLap:~/hg-octave/octave> cat myscript.m > > clear functions > > myfun > > clear functions > > kai@LxLap:~/hg-octave/octave> cat myfun.m > > function myfun > > function f1 > > function f2 > > kai@LxLap:~/hg-octave/octave> ./run-octave --silent > > adding ssprop to path > > adding optilux to path > > octave:1> myscript > > panic: Segmentation fault -- stopping myself... > > attempting to save variables to `octave-core'... > > save to `octave-core' complete > > Speicherzugriffsfehler > > kai@LxLap:~/hg-octave/octave> > > > > I have observed this with a recent tip (yesterday), but not with the > > mingw octave3.2.2 binary. Can someone confirm this crash? > > > > Nobody? I had the chance to test it on a second Opensuse system and > still see the crash, so I suspect the problem is with octave and not > with my local installation(s). I just tested this on Debian (amd64) and it crashes here as well. Sorry, no more info. I need to get some sleep now. Thomas _______________________________________________ Bug-octave mailing list Bug-octave@... https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave |
|
|
Re: octave crash with repetitive 'clear functions'Kai Habel wrote:
> -------- Original-Nachricht -------- > >> Datum: Thu, 22 Oct 2009 14:12:35 +0200 >> Von: Kai Habel <kai.habel@...> >> An: bug-octave@... >> Betreff: octave crash with repetitive \'clear functions\' >> > > >> While playing with optiplux (optilux.sf.net) again, which is written for >> octave and matlab, I ran into problems. >> >> I could reduce the problem to the following example. When running >> myscript.m, which calls myfun.m octave dies with a segmentation fault at >> the second 'clear functions'. >> >> kai@LxLap:~/hg-octave/octave> cat myscript.m >> clear functions >> myfun >> clear functions >> kai@LxLap:~/hg-octave/octave> cat myfun.m >> function myfun >> function f1 >> function f2 >> kai@LxLap:~/hg-octave/octave> ./run-octave --silent >> adding ssprop to path >> adding optilux to path >> octave:1> myscript >> panic: Segmentation fault -- stopping myself... >> attempting to save variables to `octave-core'... >> save to `octave-core' complete >> Speicherzugriffsfehler >> kai@LxLap:~/hg-octave/octave> >> >> I have observed this with a recent tip (yesterday), but not with the >> mingw octave3.2.2 binary. Can someone confirm this crash? >> >> > > Nobody? I had the chance to test it on a second Opensuse system and still see the crash, so I suspect the problem is with octave and not with my local installation(s). > > To test, create two files: > > 1.myfun.m > > function myfun > function f1 > function f2 > > 2. myscript.m > > clear functions > myfun > clear functions > > If I call myscript octave dies with a segmentation fault. > > Kai > _______________________________________________ > Bug-octave mailing list > Bug-octave@... > https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave > Segfaults in 9747:7bda650b691a. Note that if myfun.m contains no subfunctions, like myfun.m: function myfun then clear functions doesn't crash. David _______________________________________________ Bug-octave mailing list Bug-octave@... https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave |
|
|
Re: octave crash with repetitive 'clear functions'-------- Original-Nachricht --------
> Datum: Tue, 27 Oct 2009 09:25:57 +0100 > Von: David Grundberg <individ@...> > An: Kai Habel <kai.habel@...> > CC: bug@... > Betreff: Re: octave crash with repetitive \'clear functions\' > Kai Habel wrote: > > -------- Original-Nachricht -------- > > > >> Datum: Thu, 22 Oct 2009 14:12:35 +0200 > >> Von: Kai Habel <kai.habel@...> > >> An: bug-octave@... > >> Betreff: octave crash with repetitive \'clear functions\' > >> > > > > > >> While playing with optiplux (optilux.sf.net) again, which is written > for > >> octave and matlab, I ran into problems. > >> > >> I could reduce the problem to the following example. When running > >> myscript.m, which calls myfun.m octave dies with a segmentation fault > at > >> the second 'clear functions'. > >> > >> kai@LxLap:~/hg-octave/octave> cat myscript.m > >> clear functions > >> myfun > >> clear functions > >> kai@LxLap:~/hg-octave/octave> cat myfun.m > >> function myfun > >> function f1 > >> function f2 > >> kai@LxLap:~/hg-octave/octave> ./run-octave --silent > >> adding ssprop to path > >> adding optilux to path > >> octave:1> myscript > >> panic: Segmentation fault -- stopping myself... > >> attempting to save variables to `octave-core'... > >> save to `octave-core' complete > >> Speicherzugriffsfehler > >> kai@LxLap:~/hg-octave/octave> > >> > >> I have observed this with a recent tip (yesterday), but not with the > >> mingw octave3.2.2 binary. Can someone confirm this crash? > >> > >> > > > > Nobody? I had the chance to test it on a second Opensuse system and > still see the crash, so I suspect the problem is with octave and not with my > local installation(s). > > > > To test, create two files: > > > > 1.myfun.m > > > > function myfun > > function f1 > > function f2 > > > > 2. myscript.m > > > > clear functions > > myfun > > clear functions > > > > If I call myscript octave dies with a segmentation fault. > > > > Kai > > _______________________________________________ > > Bug-octave mailing list > > Bug-octave@... > > https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave > > > > > Segfaults in 9747:7bda650b691a. Note that if myfun.m contains no > subfunctions, like > > myfun.m: > > function myfun > > then clear functions doesn't crash. > > David Thanks for your confirmation. Indeed, if you remove any line of the example above, octave does not crash anymore. Kai _______________________________________________ Bug-octave mailing list Bug-octave@... https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave |
|
|
Re: octave crash with repetitive 'clear functions'-------- Original-Nachricht -------- > Datum: Tue, 27 Oct 2009 00:21:18 +0100 > Von: Thomas Weber <thomas.weber.mail@...> > An: Kai Habel <kai.habel@...> > CC: Octave Bugs <bug-octave@...> > Betreff: Re: octave crash with repetitive \'clear functions\' > Hi Kai, > > On Mon, Oct 26, 2009 at 09:09:54PM +0100, Kai Habel wrote: > > > > -------- Original-Nachricht -------- > > > Datum: Thu, 22 Oct 2009 14:12:35 +0200 > > > Von: Kai Habel <kai.habel@...> > > > An: bug-octave@... > > > Betreff: octave crash with repetitive \'clear functions\' > > > > > While playing with optiplux (optilux.sf.net) again, which is written > for > > > octave and matlab, I ran into problems. > > > > > > I could reduce the problem to the following example. When running > > > myscript.m, which calls myfun.m octave dies with a segmentation fault > at > > > the second 'clear functions'. > > > > > > kai@LxLap:~/hg-octave/octave> cat myscript.m > > > clear functions > > > myfun > > > clear functions > > > kai@LxLap:~/hg-octave/octave> cat myfun.m > > > function myfun > > > function f1 > > > function f2 > > > kai@LxLap:~/hg-octave/octave> ./run-octave --silent > > > adding ssprop to path > > > adding optilux to path > > > octave:1> myscript > > > panic: Segmentation fault -- stopping myself... > > > attempting to save variables to `octave-core'... > > > save to `octave-core' complete > > > Speicherzugriffsfehler > > > kai@LxLap:~/hg-octave/octave> > > > > > > I have observed this with a recent tip (yesterday), but not with the > > > mingw octave3.2.2 binary. Can someone confirm this crash? > > > > > > > Nobody? I had the chance to test it on a second Opensuse system and > > still see the crash, so I suspect the problem is with octave and not > > with my local installation(s). > > I just tested this on Debian (amd64) and it crashes here as well. Sorry, > no more info. I need to get some sleep now. > > Thomas Hello Thomas, thanks for your confirmation. Unfortunatly this beyond my knowledge of octave, so I have to leave the debugging to a core developer. Kai _______________________________________________ Bug-octave mailing list Bug-octave@... https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave |
|
|
Re: octave crash with repetitive 'clear functions'On 27-Oct-2009, Kai Habel wrote:
| -------- Original-Nachricht -------- | > Datum: Tue, 27 Oct 2009 00:21:18 +0100 | > Von: Thomas Weber <thomas.weber.mail@...> | > An: Kai Habel <kai.habel@...> | > CC: Octave Bugs <bug-octave@...> | > Betreff: Re: octave crash with repetitive \'clear functions\' | | > Hi Kai, | > | > On Mon, Oct 26, 2009 at 09:09:54PM +0100, Kai Habel wrote: | > > | > > -------- Original-Nachricht -------- | > > > Datum: Thu, 22 Oct 2009 14:12:35 +0200 | > > > Von: Kai Habel <kai.habel@...> | > > > An: bug-octave@... | > > > Betreff: octave crash with repetitive \'clear functions\' | > > | > > > While playing with optiplux (optilux.sf.net) again, which is written | > for | > > > octave and matlab, I ran into problems. | > > > | > > > I could reduce the problem to the following example. When running | > > > myscript.m, which calls myfun.m octave dies with a segmentation fault | > at | > > > the second 'clear functions'. | > > > | > > > kai@LxLap:~/hg-octave/octave> cat myscript.m | > > > clear functions | > > > myfun | > > > clear functions | > > > kai@LxLap:~/hg-octave/octave> cat myfun.m | > > > function myfun | > > > function f1 | > > > function f2 | > > > kai@LxLap:~/hg-octave/octave> ./run-octave --silent | > > > adding ssprop to path | > > > adding optilux to path | > > > octave:1> myscript | > > > panic: Segmentation fault -- stopping myself... | > > > attempting to save variables to `octave-core'... | > > > save to `octave-core' complete | > > > Speicherzugriffsfehler | > > > kai@LxLap:~/hg-octave/octave> | > > > | > > > I have observed this with a recent tip (yesterday), but not with the | > > > mingw octave3.2.2 binary. Can someone confirm this crash? | > > > | > > | > > Nobody? I had the chance to test it on a second Opensuse system and | > > still see the crash, so I suspect the problem is with octave and not | > > with my local installation(s). | > | > I just tested this on Debian (amd64) and it crashes here as well. Sorry, | > no more info. I need to get some sleep now. | > | > Thomas | | Hello Thomas, | | thanks for your confirmation. Unfortunatly this beyond my knowledge of octave, so I have to leave the debugging to a core developer. I checked in the following change. http://hg.savannah.gnu.org/hgweb/octave/rev/5f8971be8e12 Thanks, jwe _______________________________________________ Bug-octave mailing list Bug-octave@... https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave |
|
|
Re: octave crash with repetitive 'clear functions'John W. Eaton schrieb:
> On 27-Oct-2009, Kai Habel wrote: > > | -------- Original-Nachricht -------- > | > Datum: Tue, 27 Oct 2009 00:21:18 +0100 > | > Von: Thomas Weber <thomas.weber.mail@...> > | > An: Kai Habel <kai.habel@...> > | > CC: Octave Bugs <bug-octave@...> > | > Betreff: Re: octave crash with repetitive \'clear functions\' > | > | > Hi Kai, > | > > | > On Mon, Oct 26, 2009 at 09:09:54PM +0100, Kai Habel wrote: > | > > > | > > -------- Original-Nachricht -------- > | > > > Datum: Thu, 22 Oct 2009 14:12:35 +0200 > | > > > Von: Kai Habel <kai.habel@...> > | > > > An: bug-octave@... > | > > > Betreff: octave crash with repetitive \'clear functions\' > | > > > | > > > While playing with optiplux (optilux.sf.net) again, which is written > | > for > | > > > octave and matlab, I ran into problems. > | > > > > | > > > I could reduce the problem to the following example. When running > | > > > myscript.m, which calls myfun.m octave dies with a segmentation fault > | > at > | > > > the second 'clear functions'. > | > > > > | > > > kai@LxLap:~/hg-octave/octave> cat myscript.m > | > > > clear functions > | > > > myfun > | > > > clear functions > | > > > kai@LxLap:~/hg-octave/octave> cat myfun.m > | > > > function myfun > | > > > function f1 > | > > > function f2 > | > > > kai@LxLap:~/hg-octave/octave> ./run-octave --silent > | > > > adding ssprop to path > | > > > adding optilux to path > | > > > octave:1> myscript > | > > > panic: Segmentation fault -- stopping myself... > | > > > attempting to save variables to `octave-core'... > | > > > save to `octave-core' complete > | > > > Speicherzugriffsfehler > | > > > kai@LxLap:~/hg-octave/octave> > | > > > > | > > > I have observed this with a recent tip (yesterday), but not with the > | > > > mingw octave3.2.2 binary. Can someone confirm this crash? > | > > > > | > > > | > > Nobody? I had the chance to test it on a second Opensuse system and > | > > still see the crash, so I suspect the problem is with octave and not > | > > with my local installation(s). > | > > | > I just tested this on Debian (amd64) and it crashes here as well. Sorry, > | > no more info. I need to get some sleep now. > | > > | > Thomas > | > | Hello Thomas, > | > | thanks for your confirmation. Unfortunatly this beyond my knowledge of octave, so I have to leave the debugging to a core developer. > > I checked in the following change. > > http://hg.savannah.gnu.org/hgweb/octave/rev/5f8971be8e12 > > Thanks, > > jwe > systems. Kai _______________________________________________ Bug-octave mailing list Bug-octave@... https://www-old.cae.wisc.edu/mailman/listinfo/bug-octave |
| Free embeddable forum powered by Nabble | Forum Help |