[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: |
Mike Miller |
Subject: |
[Octave-bug-tracker] [bug #50068] Segfault, when eval_string is used in interpreter embedded mode |
Date: |
Wed, 18 Jan 2017 07:27:32 +0000 (UTC) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0 |
Follow-up Comment #3, bug #50068 (project octave):
I agree that these examples, and my own tests, modified from the provided
embedded.cc boilerplate example, succeed with Octave 4.0.x but fail on the
default branch. I don't have a working 4.2 to test at the moment, but I expect
it is similar to default at this point.
The segfault occurs at
Thread 1 "embedded" received signal SIGSEGV, Segmentation fault.
0x00007ffff6e69aea in octave::application::interactive () at
../libinterp/octave.cc:362
362 interpreter *interp = instance->m_interpreter;
(gdb) bt
#0 0x00007ffff6e69aea in octave::application::interactive () at
../libinterp/octave.cc:362
#1 0x00007ffff739f22b in octave::base_lexer::reset (this=0x555555dc4bc0) at
../libinterp/parse-tree/lex.ll:2327
#2 0x00007ffff73ad1c4 in octave::base_parser::reset
(address@hidden) at libinterp/parse-tree/oct-parse.yy:2161
#3 0x00007ffff73b77bf in eval_string (eval_str="who",
address@hidden, address@hidden: 0,
address@hidden) at libinterp/parse-tree/oct-parse.yy:5058
#4 0x00007ffff73b7d40 in eval_string (eval_str="who", silent=<optimized out>,
address@hidden: 0) at libinterp/parse-tree/oct-parse.yy:5121
#5 0x00005555555563a8 in main () at embedded.cc:23
_______________________________________________________
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, Dmitry Messerman, 2017/01/17
- [Octave-bug-tracker] [bug #50068] Segfault, when eval_string is used in interpreter embedded mode, Rik, 2017/01/17
- [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,
Mike Miller <=
- [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, 2017/01/18