[Octave-bug-tracker] [bug #42626] Crashes with no warning - what can I do to help?

[Mike Miller]

Update of bug #42626 (project octave):

                Category:                    None => Interpreter            
              Item Group:                    None => Crash                  
                  Status:                    None => Need Info              

    _______________________________________________________

Follow-up Comment #1:

Thanks for your bug report. Yes, we will need much more information. Is your
piece of code a compiled oct-file or mex-file, or is it scripts or functions
in m-files? If your code is compiled, there is a possibility that your
function may be bringing the segmentation fault. If your code is purely
m-files, then this is potentially a bug in Octave.

Can you share your code? Or can you create a minimal example that demonstrates
the same error and share that?

If you can't share your code so that we can reproduce it, can you install the
octave-dbg package from Debian testing and get a stack trace of the error? See
http://wiki.octave.org/Debugging_Octave, ignoring the parts about rebuilding
Octave because the octave-dbg package ensures you have debug symbols.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?42626>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/