[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: |
Mike Miller |
Subject: |
[Octave-bug-tracker] [bug #36161] segfault when using octave_map with g++ --std=c++11 |
Date: |
Sat, 20 Apr 2013 22:10:07 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.63 Safari/537.31 |
Update of bug #36161 (project octave):
Category: None => Libraries
_______________________________________________________
Follow-up Comment #13:
I also cannot reproduce this:
$ g++-4.7 --version
g++-4.7 (Debian 4.7.2-5) 4.7.2
Copyright (C) 2012 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
$ g++-4.7 -std=c++11 test.cpp -o test -I/usr/include/octave-3.6.4 -loctave
-loctinterp
$ valgrind ./test
Output looks clean, no segfault. Also fine with 3.6.1 and development version.
Does this still affect OP?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?36161>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Octave-bug-tracker] [bug #36161] segfault when using octave_map with g++ --std=c++11,
Mike Miller <=