|
From: | Markus Mützel |
Subject: | [Octave-bug-tracker] [bug #61191] eval can cause a crash to desktop |
Date: | Mon, 20 Sep 2021 09:46:17 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/93.0.4577.82 Safari/537.36 Edg/93.0.961.52 |
Update of bug #61191 (project octave): Severity: 3 - Normal => 4 - Important Priority: 5 - Normal => 7 - High Status: None => Confirmed Operating System: Microsoft Windows => Any _______________________________________________________ Follow-up Comment #1: I can confirm the crash also with Octave 6.3.0 and Octave 7.0.0 (hg id 41eecdf76372) on Windows. Same with Octave 7.0.0 (hg id 813b7827c5f8) on Ubuntu 20.10 (with `bugscript.m` in `./a`): octave:1> addpath a octave:2> omc_1=rand(3,1); octave:3> Tc_1=rand(3,1); octave:4> bugscript panic: impossible state reached in file '../libinterp/corefcn/stack-frame.cc' at line 1264 fatal: caught signal Aborted -- stopping myself... Aborted (core dumped) Raising priority and severity because this is a hard crash with the potential of a user losing data. The commands look quite simple to me and I wouldn't expect an error/crash. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?61191> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |