You can subscribe to this list here.
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(5) |
Nov
(5) |
Dec
(1) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2010 |
Jan
|
Feb
(4) |
Mar
(1) |
Apr
(10) |
May
|
Jun
(1) |
Jul
|
Aug
(1) |
Sep
(4) |
Oct
|
Nov
|
Dec
|
2011 |
Jan
(1) |
Feb
(1) |
Mar
(2) |
Apr
|
May
(30) |
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
2012 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
(2) |
Aug
(2) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(1) |
2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
S | M | T | W | T | F | S |
---|---|---|---|---|---|---|
|
1
|
2
|
3
|
4
|
5
|
6
|
7
|
8
|
9
|
10
|
11
|
12
|
13
|
14
|
15
|
16
|
17
|
18
|
19
|
20
|
21
|
22
|
23
|
24
|
25
|
26
|
27
|
28
(1) |
29
(1) |
30
|
31
|
|
|
|
From: Stephan B. <sg...@go...> - 2013-07-29 20:09:31
|
On Sun, Jul 28, 2013 at 8:01 PM, Joakim Hove <jo...@st...> wrote: > As you can see I have a very old version of g++ (4.1.2). I am in a > corporate environment and it is quite painful to get a newer version – do > you think this can be the problem? > i don't know if this will help, but a quick google reveals several people complaining of buggy gcc 4.1 behaviours at specific optimization levels. Maybe try with, e.g. -O0 and -O2? http://de.comp.lang.c.narkive.com/dl6LsJPL/ot-gcc-4-1-1-buggy-optimierungsstufe-3 that thread has a bit about "the optimizing away of a function which provably has no side effect": 'Das "wegoptimieren von Funktionen, die gemaess ihrer Spezifikation keine Nebenwirkungen haben" ist kein Fehler.' (sorry, didn't find a decent english one.) which might be what's happening to you? That shouldn't cause a segfault, but it might be related. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal |
From: Joakim H. <jo...@st...> - 2013-07-28 18:01:56
|
Hello, I have downloaded jsoncpp and successfully built it; I also issued the command "scons platform=linux-gcc check" to run the tests - the all passed. I then created my own program to actually test this; the program compiles and links fine - but it goes down witn SIGSEGV when running. My program is #include <json/json.h> void parseJson() { Json::Reader reader; } int main(int argc , char ** argv) { parseJson(); exit(0); } I.e. it is very simple stuff. When I try putting the Json::Reader instance in the boyd of main{...} it seems to work. A backtrace from gdb is inlined below: #0 0x0000003a560b7672 in __gnu_cxx::__exchange_and_add () from /usr/lib64/libstdc++.so.6 #1 0x0000000000403313 in std::string::_Rep::_M_dispose (this=0xffffffffffffffe9, __a=@0x7fff7fb14957) at /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:232 #2 0x0000000000403360 in ~basic_string (this=0x7fff7fb14ab0) at /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:478 #3 0x00000000004039fe in ~Reader (this=0x7fff7fb149b0) at /private/joaho/Parser/opm-parser/external/json/json-cpp/include/json/reader.h:23 #4 0x0000000000402aba in parseJson () at /private/joaho/Parser/opm-parser/opm/parser/eclipse/ExternalTests/ExternalTests.cpp:50 #5 0x0000000000402ad5 in main (argc=1, argv=0x7fff7fb14bc8) at /private/joaho/Parser/opm-parser/opm/parser/eclipse/ExternalTests/ExternalTests.cpp:55 As you can see I have a very old version of g++ (4.1.2). I am in a corporate environment and it is quite painful to get a newer version - do you think this can be the problem? Regards Joakim ------------------------------------------------------------------- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you |