same code, same library version, same compiler, different output











up vote
4
down vote

favorite












File h.cpp



#include "yaml-cpp/yaml.h"

#include <iostream>

int main() {

    YAML::Node node = YAML::Load("[1, 2, 3]");

    std::cout << node << "n";

    std::cout << node.Type() << "n";

    std::cout << node.IsSequence() << "n";

}


compiled and executed with



g++ -lyaml-cpp h.cpp && ./a.out


yields



[1, 2, 3]

3

1


on my desktop, but



[1, 2, 3]

1

0


on my laptop. The last line of laptop output is wrong: For sure, the given YAML string is a sequence.



Same results when g++ is replaced by clang++. Both machines run the same Debian 4.18.10-2, both are x86_64, both run Linux 4.18.0-2-amd64, both have same versions of g++ and clang++. Both have the same yaml-cpp library versions, freshly reinstalled:



$ locate libyaml-cpp.

/usr/lib/x86_64-linux-gnu/libyaml-cpp.a

/usr/lib/x86_64-linux-gnu/libyaml-cpp.so

/usr/lib/x86_64-linux-gnu/libyaml-cpp.so.0.5

/usr/lib/x86_64-linux-gnu/libyaml-cpp.so.0.5.2



$ dpkg -S /usr/lib/x86_64-linux-gnu/libyaml-cpp.a

libyaml-cpp-dev: /usr/lib/x86_64-linux-gnu/libyaml-cpp.a

$ dpkg -S /usr/lib/x86_64-linux-gnu/libyaml-cpp.so.0.5.2

libyaml-cpp0.5v5:amd64: /usr/lib/x86_64-linux-gnu/libyaml-cpp.so.0.5.2



$ apt-cache show libyaml-cpp-dev

Package: libyaml-cpp-dev

Source: yaml-cpp

Version: 0.5.2-4

$ apt-cache show libyaml-cpp0.5v5

Package: libyaml-cpp0.5v5

Source: yaml-cpp

Version: 0.5.2-4


Output from ldd is identical except for the hex addresses in parentheses:



$ ldd a.out

    linux-vdso.so.1 (0x00007ffd0d5f0000)

    libyaml-cpp.so.0.5 => /usr/lib/x86_64-linux-gnu/libyaml-cpp.so.0.5 (0x00007f1e9fcd8000)

    libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f1e9fb55000)

    libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f1e9f9c1000)

    libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f1e9f9a7000)

    libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f1e9f7ea000)

    /lib64/ld-linux-x86-64.so.2 (0x00007f1e9ff79000)


What possible explanations remain in such a situation?






c++ yaml-cpp







share|improve this question




















  • 2




    You may not be running the a.out you think you are running in one or both environments, especially if the PATH differs between the two. Avoid this risk by specifically executing ./a.out instead of relying on a path lookup to find the executable.
    – John Bollinger
    Nov 9 at 22:46












  • Valid point, but not the explanation here. I'll edit the question to rule out this possibility.
    – Joachim W
    Nov 9 at 23:05






  • 1




    The most reasonable explanation is the YAML library is having undefined behavior. You can try running it under sanitizers or manually check the code.
    – Dani
    Nov 9 at 23:09










  • It might be helpful to see what this outputs: std::cout << node.Type() << " : " << YAML::NodeType::Sequence << "n";
    – David Schwartz
    Nov 10 at 0:04










  • node.Type() output also differs, 3 vs 1
    – Joachim W
    Nov 10 at 6:16















up vote
4
down vote

favorite












File h.cpp



#include "yaml-cpp/yaml.h"

#include <iostream>

int main() {

    YAML::Node node = YAML::Load("[1, 2, 3]");

    std::cout << node << "n";

    std::cout << node.Type() << "n";

    std::cout << node.IsSequence() << "n";

}


compiled and executed with



g++ -lyaml-cpp h.cpp && ./a.out


yields



[1, 2, 3]

3

1


on my desktop, but



[1, 2, 3]

1

0


on my laptop. The last line of laptop output is wrong: For sure, the given YAML string is a sequence.



Same results when g++ is replaced by clang++. Both machines run the same Debian 4.18.10-2, both are x86_64, both run Linux 4.18.0-2-amd64, both have same versions of g++ and clang++. Both have the same yaml-cpp library versions, freshly reinstalled:



$ locate libyaml-cpp.

/usr/lib/x86_64-linux-gnu/libyaml-cpp.a

/usr/lib/x86_64-linux-gnu/libyaml-cpp.so

/usr/lib/x86_64-linux-gnu/libyaml-cpp.so.0.5

/usr/lib/x86_64-linux-gnu/libyaml-cpp.so.0.5.2



$ dpkg -S /usr/lib/x86_64-linux-gnu/libyaml-cpp.a

libyaml-cpp-dev: /usr/lib/x86_64-linux-gnu/libyaml-cpp.a

$ dpkg -S /usr/lib/x86_64-linux-gnu/libyaml-cpp.so.0.5.2

libyaml-cpp0.5v5:amd64: /usr/lib/x86_64-linux-gnu/libyaml-cpp.so.0.5.2



$ apt-cache show libyaml-cpp-dev

Package: libyaml-cpp-dev

Source: yaml-cpp

Version: 0.5.2-4

$ apt-cache show libyaml-cpp0.5v5

Package: libyaml-cpp0.5v5

Source: yaml-cpp

Version: 0.5.2-4


Output from ldd is identical except for the hex addresses in parentheses:



$ ldd a.out

    linux-vdso.so.1 (0x00007ffd0d5f0000)

    libyaml-cpp.so.0.5 => /usr/lib/x86_64-linux-gnu/libyaml-cpp.so.0.5 (0x00007f1e9fcd8000)

    libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f1e9fb55000)

    libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f1e9f9c1000)

    libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f1e9f9a7000)

    libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f1e9f7ea000)

    /lib64/ld-linux-x86-64.so.2 (0x00007f1e9ff79000)


What possible explanations remain in such a situation?






c++ yaml-cpp







share|improve this question




















  • 2




    You may not be running the a.out you think you are running in one or both environments, especially if the PATH differs between the two. Avoid this risk by specifically executing ./a.out instead of relying on a path lookup to find the executable.
    – John Bollinger
    Nov 9 at 22:46












  • Valid point, but not the explanation here. I'll edit the question to rule out this possibility.
    – Joachim W
    Nov 9 at 23:05






  • 1




    The most reasonable explanation is the YAML library is having undefined behavior. You can try running it under sanitizers or manually check the code.
    – Dani
    Nov 9 at 23:09










  • It might be helpful to see what this outputs: std::cout << node.Type() << " : " << YAML::NodeType::Sequence << "n";
    – David Schwartz
    Nov 10 at 0:04










  • node.Type() output also differs, 3 vs 1
    – Joachim W
    Nov 10 at 6:16













up vote
4
down vote

favorite









up vote
4
down vote

favorite











File h.cpp



#include "yaml-cpp/yaml.h"

#include <iostream>

int main() {

    YAML::Node node = YAML::Load("[1, 2, 3]");

    std::cout << node << "n";

    std::cout << node.Type() << "n";

    std::cout << node.IsSequence() << "n";

}


compiled and executed with



g++ -lyaml-cpp h.cpp && ./a.out


yields



[1, 2, 3]

3

1


on my desktop, but



[1, 2, 3]

1

0


on my laptop. The last line of laptop output is wrong: For sure, the given YAML string is a sequence.



Same results when g++ is replaced by clang++. Both machines run the same Debian 4.18.10-2, both are x86_64, both run Linux 4.18.0-2-amd64, both have same versions of g++ and clang++. Both have the same yaml-cpp library versions, freshly reinstalled:



$ locate libyaml-cpp.

/usr/lib/x86_64-linux-gnu/libyaml-cpp.a

/usr/lib/x86_64-linux-gnu/libyaml-cpp.so

/usr/lib/x86_64-linux-gnu/libyaml-cpp.so.0.5

/usr/lib/x86_64-linux-gnu/libyaml-cpp.so.0.5.2



$ dpkg -S /usr/lib/x86_64-linux-gnu/libyaml-cpp.a

libyaml-cpp-dev: /usr/lib/x86_64-linux-gnu/libyaml-cpp.a

$ dpkg -S /usr/lib/x86_64-linux-gnu/libyaml-cpp.so.0.5.2

libyaml-cpp0.5v5:amd64: /usr/lib/x86_64-linux-gnu/libyaml-cpp.so.0.5.2



$ apt-cache show libyaml-cpp-dev

Package: libyaml-cpp-dev

Source: yaml-cpp

Version: 0.5.2-4

$ apt-cache show libyaml-cpp0.5v5

Package: libyaml-cpp0.5v5

Source: yaml-cpp

Version: 0.5.2-4


Output from ldd is identical except for the hex addresses in parentheses:



$ ldd a.out

    linux-vdso.so.1 (0x00007ffd0d5f0000)

    libyaml-cpp.so.0.5 => /usr/lib/x86_64-linux-gnu/libyaml-cpp.so.0.5 (0x00007f1e9fcd8000)

    libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f1e9fb55000)

    libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f1e9f9c1000)

    libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f1e9f9a7000)

    libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f1e9f7ea000)

    /lib64/ld-linux-x86-64.so.2 (0x00007f1e9ff79000)


What possible explanations remain in such a situation?






c++ yaml-cpp







share|improve this question















File h.cpp



#include "yaml-cpp/yaml.h"

#include <iostream>

int main() {

    YAML::Node node = YAML::Load("[1, 2, 3]");

    std::cout << node << "n";

    std::cout << node.Type() << "n";

    std::cout << node.IsSequence() << "n";

}


compiled and executed with



g++ -lyaml-cpp h.cpp && ./a.out


yields



[1, 2, 3]

3

1


on my desktop, but



[1, 2, 3]

1

0


on my laptop. The last line of laptop output is wrong: For sure, the given YAML string is a sequence.



Same results when g++ is replaced by clang++. Both machines run the same Debian 4.18.10-2, both are x86_64, both run Linux 4.18.0-2-amd64, both have same versions of g++ and clang++. Both have the same yaml-cpp library versions, freshly reinstalled:



$ locate libyaml-cpp.

/usr/lib/x86_64-linux-gnu/libyaml-cpp.a

/usr/lib/x86_64-linux-gnu/libyaml-cpp.so

/usr/lib/x86_64-linux-gnu/libyaml-cpp.so.0.5

/usr/lib/x86_64-linux-gnu/libyaml-cpp.so.0.5.2



$ dpkg -S /usr/lib/x86_64-linux-gnu/libyaml-cpp.a

libyaml-cpp-dev: /usr/lib/x86_64-linux-gnu/libyaml-cpp.a

$ dpkg -S /usr/lib/x86_64-linux-gnu/libyaml-cpp.so.0.5.2

libyaml-cpp0.5v5:amd64: /usr/lib/x86_64-linux-gnu/libyaml-cpp.so.0.5.2



$ apt-cache show libyaml-cpp-dev

Package: libyaml-cpp-dev

Source: yaml-cpp

Version: 0.5.2-4

$ apt-cache show libyaml-cpp0.5v5

Package: libyaml-cpp0.5v5

Source: yaml-cpp

Version: 0.5.2-4


Output from ldd is identical except for the hex addresses in parentheses:



$ ldd a.out

    linux-vdso.so.1 (0x00007ffd0d5f0000)

    libyaml-cpp.so.0.5 => /usr/lib/x86_64-linux-gnu/libyaml-cpp.so.0.5 (0x00007f1e9fcd8000)

    libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f1e9fb55000)

    libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f1e9f9c1000)

    libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f1e9f9a7000)

    libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f1e9f7ea000)

    /lib64/ld-linux-x86-64.so.2 (0x00007f1e9ff79000)


What possible explanations remain in such a situation?






c++ yaml-cpp




c++ yaml-cpp






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 10 at 21:28

























asked Nov 9 at 22:41









Joachim W

2,35831329




2,35831329








  • 2




    You may not be running the a.out you think you are running in one or both environments, especially if the PATH differs between the two. Avoid this risk by specifically executing ./a.out instead of relying on a path lookup to find the executable.
    – John Bollinger
    Nov 9 at 22:46












  • Valid point, but not the explanation here. I'll edit the question to rule out this possibility.
    – Joachim W
    Nov 9 at 23:05






  • 1




    The most reasonable explanation is the YAML library is having undefined behavior. You can try running it under sanitizers or manually check the code.
    – Dani
    Nov 9 at 23:09










  • It might be helpful to see what this outputs: std::cout << node.Type() << " : " << YAML::NodeType::Sequence << "n";
    – David Schwartz
    Nov 10 at 0:04










  • node.Type() output also differs, 3 vs 1
    – Joachim W
    Nov 10 at 6:16














  • 2




    You may not be running the a.out you think you are running in one or both environments, especially if the PATH differs between the two. Avoid this risk by specifically executing ./a.out instead of relying on a path lookup to find the executable.
    – John Bollinger
    Nov 9 at 22:46












  • Valid point, but not the explanation here. I'll edit the question to rule out this possibility.
    – Joachim W
    Nov 9 at 23:05






  • 1




    The most reasonable explanation is the YAML library is having undefined behavior. You can try running it under sanitizers or manually check the code.
    – Dani
    Nov 9 at 23:09










  • It might be helpful to see what this outputs: std::cout << node.Type() << " : " << YAML::NodeType::Sequence << "n";
    – David Schwartz
    Nov 10 at 0:04










  • node.Type() output also differs, 3 vs 1
    – Joachim W
    Nov 10 at 6:16








2




2




You may not be running the a.out you think you are running in one or both environments, especially if the PATH differs between the two. Avoid this risk by specifically executing ./a.out instead of relying on a path lookup to find the executable.
– John Bollinger
Nov 9 at 22:46






You may not be running the a.out you think you are running in one or both environments, especially if the PATH differs between the two. Avoid this risk by specifically executing ./a.out instead of relying on a path lookup to find the executable.
– John Bollinger
Nov 9 at 22:46














Valid point, but not the explanation here. I'll edit the question to rule out this possibility.
– Joachim W
Nov 9 at 23:05




Valid point, but not the explanation here. I'll edit the question to rule out this possibility.
– Joachim W
Nov 9 at 23:05




1




1




The most reasonable explanation is the YAML library is having undefined behavior. You can try running it under sanitizers or manually check the code.
– Dani
Nov 9 at 23:09




The most reasonable explanation is the YAML library is having undefined behavior. You can try running it under sanitizers or manually check the code.
– Dani
Nov 9 at 23:09












It might be helpful to see what this outputs: std::cout << node.Type() << " : " << YAML::NodeType::Sequence << "n";
– David Schwartz
Nov 10 at 0:04




It might be helpful to see what this outputs: std::cout << node.Type() << " : " << YAML::NodeType::Sequence << "n";
– David Schwartz
Nov 10 at 0:04












node.Type() output also differs, 3 vs 1
– Joachim W
Nov 10 at 6:16




node.Type() output also differs, 3 vs 1
– Joachim W
Nov 10 at 6:16

















active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














 

draft saved


draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53234192%2fsame-code-same-library-version-same-compiler-different-output%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















 

draft saved


draft discarded



















































 


draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53234192%2fsame-code-same-library-version-same-compiler-different-output%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-

Popular posts from this blog

Bressuire

Image
Subprefecture and commune in Nouvelle-Aquitaine, France Bressuire Subprefecture and commune Chateau de Bressuire and the Eglise Notre-Dame Coat of arms Location of Bressuire Bressuire Show map of France Bressuire Show map of Nouvelle-Aquitaine Coordinates: 46°50′27″N 0°29′14″W  /  46.8408°N 0.4872°W  / 46.8408; -0.4872 Coordinates: 46°50′27″N 0°29′14″W  /  46.8408°N 0.4872°W  / 46.8408; -0.4872 Country France Region Nouvelle-Aquitaine Department Deux-Sèvres Arrondissement Bressuire Canton Bressuire Government  • Mayor .mw-parser-output .nobold{font-weight:normal} (2014–20) Jean Michel Bernier Area 1 180.59 km 2 (69.73 sq mi) Population (2014) 2 19,300  • Density 110/km 2 (280/sq mi) Time zone UTC+01:00 (CET)  • Summer (DST) UTC+02:00 (CEST) INSEE/Postal code 79049 /79300 Elevation 98–236 m (322–774 ft) (avg. 173 m or 568 ft) 1 French Land Register data, which exclude
Read more

Vorschmack

Image
Vorschmack Ukrainian Jewish-style vorschmack served on rye bread Course Hors d'oeuvre Region or state Eastern Europe Associated national cuisine Ashkenazi Jewish, Finnish, German, Ukrainian, Polish, Russian Main ingredients Ground meat and/or fish Cookbook: Vorschmack   Media: Vorschmack Vorschmack or forshmak (Yiddish: פֿאָרשמאַק ‎, from archaic German Vorschmack , "foretaste" [1] or "appetizer" [2] ) is an originally East European dish made of salty minced fish or meat. Different variants of this dish are especially common in Ashkenazi Jewish and Finnish cuisine. Some varieties are also known in Russian and Polish cuisine. Contents 1 In Jewish cuisine 2 In Russian cuisine 3 In Polish cuisine 4 In Finnish cuisine 5 See also 6 References In Jewish cuisine According to Gil Marks, the German name points to the possible Germanic origin of this dish. [1] William Pokhlyobkin descr
Read more

Quarantine

Image
For other uses, see Quarantine (disambiguation). Signal flag "Lima" called the "Yellow Jack" which when flown in harbor means ship is under quarantine. A simple yellow flag (also called the "Yellow Jack") had historically been used to signal quarantine (it stands for Q among signal flags), but now indicates the opposite, as a signal of a ship free of disease that requests boarding and inspection. A quarantine is used to separate and restrict the movement of people; it is 'a restraint upon the activities or communication of persons or the transport of goods designed to prevent the spread of disease or pests', for a certain period of time. [1] This is often used in connection to disease and illness, such as those who may possibly have been exposed to a communicable disease. [2] The term is often erroneously used to mean medical isolation, which is "to separate ill persons who have a communicable disease from those who are healthy
Read more