|
From: | Dmitri A. Sergatskov |
Subject: | [Octave-bug-tracker] [bug #57350] Recursive behavior of graphic callbacks has changed |
Date: | Tue, 3 Dec 2019 16:43:08 -0500 (EST) |
User-agent: | Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0 |
Follow-up Comment #6, bug #57350 (project octave): I applied the patch, but the behavior looks the same. The core dump trace is much shorter though... ./run-octave -q -f octave:1> __octave_config_info__ ("hg_id") ans = cd566153edd6+ octave:2> tst_recur stopped in updater at line 2 [/home/dima/src/octave/gcc_def/updater.m] 2: keyboard; keyboard> fatal: caught signal Segmentation fault -- stopping myself... Segmentation fault (core dumped) Dec 03 15:38:57 i7 systemd-coredump[215121]: Process 214976 (lt-octave-gui) of user 1001 dumped core. Stack trace of thread 215115: #0 0x00007f607c48ed3e n/a (/home/dima/src/octave/gcc_def/libinterp/.libs/liboctinterp.so.7.0.0) Dec 03 15:38:57 i7 systemd[1]: systemd-coredump@5-215120-0.service: Succeeded. Dmitri. -- _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?57350> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |