[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #50068] Segfault, when eval_string is used in
From: |
Dmitry Messerman |
Subject: |
[Octave-bug-tracker] [bug #50068] Segfault, when eval_string is used in interpreter embedded mode |
Date: |
Wed, 18 Jan 2017 18:04:07 +0000 (UTC) |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0 |
Follow-up Comment #13, bug #50068 (project octave):
One more comment.
With regards to the Rik's response.
1) Vanilla code from Appendix A does not reproduce problem, which is reported
in the ticket, as feval works fine both in 4.0.2 and 4.2.0
In order to reproduce problem, which is is reported in the ticket, I'm aware
of 2 ways:
- Use eval_string: example is attached in original submission
- Use source_file: if needed, I can create example of this one
as well
2) Exception thrown by cleanup_and_exit is another issue.
I've not reported it, as it has trivial workaround:
use try - catch brackets.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?50068>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #50068] Segfault, when eval_string is used in interpreter embedded mode, (continued)
- [Octave-bug-tracker] [bug #50068] Segfault, when eval_string is used in interpreter embedded mode, Mike Miller, 2017/01/18
- [Octave-bug-tracker] [bug #50068] Segfault, when eval_string is used in interpreter embedded mode, Mike Miller, 2017/01/18
- [Octave-bug-tracker] [bug #50068] Segfault, when eval_string is used in interpreter embedded mode, Dmitry Messerman, 2017/01/18
- [Octave-bug-tracker] [bug #50068] Segfault, when eval_string is used in interpreter embedded mode, Dmitry Messerman, 2017/01/18
- [Octave-bug-tracker] [bug #50068] Segfault, when eval_string is used in interpreter embedded mode, Rik, 2017/01/18
- [Octave-bug-tracker] [bug #50068] Segfault, when eval_string is used in interpreter embedded mode, Mike Miller, 2017/01/18
- [Octave-bug-tracker] [bug #50068] Segfault, when eval_string is used in interpreter embedded mode, Mike Miller, 2017/01/18
- [Octave-bug-tracker] [bug #50068] Segfault, when eval_string is used in interpreter embedded mode, Dmitry Messerman, 2017/01/18
- [Octave-bug-tracker] [bug #50068] Segfault, when eval_string is used in interpreter embedded mode, John W. Eaton, 2017/01/18
- [Octave-bug-tracker] [bug #50068] Segfault, when eval_string is used in interpreter embedded mode, John W. Eaton, 2017/01/18
- [Octave-bug-tracker] [bug #50068] Segfault, when eval_string is used in interpreter embedded mode,
Dmitry Messerman <=
- [Octave-bug-tracker] [bug #50068] Segfault, when eval_string is used in interpreter embedded mode, John W. Eaton, 2017/01/20
- [Octave-bug-tracker] [bug #50068] Segfault, when eval_string is used in interpreter embedded mode, Dmitry Messerman, 2017/01/21
- [Octave-bug-tracker] [bug #50068] Segfault, when eval_string is used in interpreter embedded mode, Rik, 2017/01/21
- [Octave-bug-tracker] [bug #50068] Segfault, when eval_string is used in interpreter embedded mode, John W. Eaton, 2017/01/24
- [Octave-bug-tracker] [bug #50068] Segfault, when eval_string is used in interpreter embedded mode, Rik, 2017/01/27
- [Octave-bug-tracker] [bug #50068] Segfault, when eval_string is used in interpreter embedded mode, John W. Eaton, 2017/01/27
- [Octave-bug-tracker] [bug #50068] Segfault, when eval_string is used in interpreter embedded mode, Dmitry Messerman, 2017/01/29
- [Octave-bug-tracker] [bug #50068] Segfault, when eval_string is used in interpreter embedded mode, Rik, 2017/01/29