|
From: | John W. Eaton |
Subject: | [Octave-bug-tracker] [bug #65468] fatal: caught signal Trace/BPT trap: 5 -- stopping myself... |
Date: | Tue, 19 Mar 2024 15:39:10 -0400 (EDT) |
Follow-up Comment #5, bug #65468 (group octave): I guess the gdb command "catch signal NUM" has a different syntax in lldb or is not an available feature? After you issue the lldb "continue" command you are executing the quit command at the Octave prompt? I don't know what libunwind is used for. I don't think Octave is using it directly. Can you get a stack trace at the point where the Octave process is stopping? Those instructions displayed by lldb when the process stops don't help much here. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?65468> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |