[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #49296] Visual Studio build issue

From: Bill Greene
Subject: [Octave-bug-tracker] [bug #49296] Visual Studio build issue
Date: Sat, 8 Oct 2016 14:15:39 +0000 (UTC)
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36


                 Summary: Visual Studio build issue
                 Project: GNU Octave
            Submitted by: billgreene
            Submitted on: Sat 08 Oct 2016 02:15:36 PM GMT
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.2.0-rc2
        Operating System: Microsoft Windows



With Octave 4.0.x, I was able to build mex files with Visual Studio with no
problems. With 4.2.0-rc2, there apparently is now an incompatibility between
the C++ exception handling in VS and Octave/MingW.

When my code calls, e.g. mexErrMsgIdAndTxt from the mex dll built with VS,
Octave crashes. If I run Octave in gdb, I get the following error message:
terminate called after throwing an instance of 'octave::execution_exception'

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
panic: Aborted -- stopping myself...
attempting to save variables to 'octave-workspace'...
save to 'octave-workspace' complete

Program received signal SIGSEGV, Segmentation fault.
0x6feaec92 in libstdc++-6!_ZSt18_Rb_tree_incrementPSt18_Rb_tree_node_base ()
   from C:\octave\Octave-4.2.0-rc2\bin\libstdc++-6.dll

Not surprisingly, the mex dll works fine if built with mkoctfile. But I have
found the VS GUI to be a much more convenient environment for building mex
modules and am disappointed this appears to be no longer possible.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]