[Octave-bug-tracker] [bug #36161] segfault when using octave_map with g++ --std=c++11

[nope]

Follow-up Comment #7, bug #36161 (project octave):

I confirm that the bug appears with gcc 4.7.0 and does not appear with earlier
versions.

@jordigh

I realize this isn't a major bug. I just thought there was a chance that some
core developer knew how to fix it right away and slip it in before the new
release :) 

I am not using octave to create oct files. I use it in some research code for
my master thesis, and the whole project is compiled using c++11 (I use auto
and lambdas all over the place).

I am also not using mkoctfile because my program is generated using
CMake/Makefiles. Is there something inherently wrong with linking to the
octave libs without mkoctfile?

@bpabbott:
> What do you change to enable c++11 support ?

What do you mean? I use the --std=c++11 flag to enable C++11 support.

For the time being, I can work around this bug  by removing the destructor
(~dim_vector()) in dim_vector.h. I know it is not pretty, but I haven't found
the real problem yet.

    _______________________________________________________

Reply to this item at:

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

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