octave-bug-tracker
[Top][All Lists]
Advanced
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #36161] segfault when using octave_map with g+

From: Jordi Gutiérrez Hermoso
Subject: [Octave-bug-tracker] [bug #36161] segfault when using octave_map with g++ --std=c++11
Date: Fri, 13 Apr 2012 13:43:38 +0000
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20110109 Hypergoose/3.6.13 
Update of bug #36161 (project octave):

                  Status:               Need Info => Works For Me           

    _______________________________________________________

Follow-up Comment #5:

By the way, you should be compiling with mkoctfile:


CXXFLAGS='-std=c++0x' mkoctfile test.cc --link-stand-alone


I can't reproduce this valgrind output on gcc 4.4.5, so I'm inclined to think
it's the compiler that's at fault, not Octave.

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/
reply via email to
[Prev in Thread] Current Thread [Next in Thread]