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

Xamarin.iOS Cant Deploy on Iphone

Image
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box; } -1 I have a windows laptop and a mac mini my problem is that It wont deploy on iphone if I use Visual Studio Xamarin on windows to install my app, but it works fine with Visual Studio For Mac. Here's what I get after build succeded on Visual Studio Xamarin on windows : 1>------ Build started: Project: FinalCustomerApp.iOS, Configuration: Debug iPhone ------ 1> Connecting to Mac server 192.168.8.100... 1> FinalCustomerApp.iOS -> C:UsersJeremy PaulDesktopFinalCustomerAppFinalCustomerAppFinalCustomerApp.iOSbiniPhoneDebugFinalCustomerApp.iOS.exe 1> Detected signing identity: 1> Code Signing Key: &quo
Read more

Glorious Revolution

Image
"The Bloodless Revolution" redirects here. For a history of the vegetarian movement, see The Bloodless Revolution (book). This article is about the English revolution of 1688. For the revolution of 1868 in Spain, see Glorious Revolution (Spain). For other uses, see Glorious Revolution (disambiguation). Glorious Revolution The Prince of Orange lands at Torbay Date 1688–1689 Location British Isles Also known as Revolution of 1688 War of the English Succession Bloodless Revolution Participants English, Welsh and Scottish society, Dutch forces Outcome Replacement of James II by William III and Mary II Jacobite rising of 1689 Williamite War in Ireland War with France; England and Scotland join Grand Alliance Drafting of the Bill of Rights 1689 Part of a series on the History of England Timeline Prehistoric Britain Roman Britain Sub-Roman Britain Medieval period Economy in the Middle Ages Anglo-Saxon period
Read more

Dulmage-Mendelsohn matrix decomposition in Python

Image
0 Matlab has a function called dmperm that computes the so-called Dulmage–Mendelsohn decomposition of a n x n matrix. From wikipedia, the Dulmage–Mendelsohn is a partition of the vertices of a bipartite graph into subsets, with the property that two adjacent vertices belong to the same subset if and only if they are paired with each other in a perfect matching of the graph. Looking both on scipy and numpy, I could not find this function, nor some similar version. Is it possible to implement it using basic linear algebra operations? Any idea if this is implemented in some Python package? python matlab linear-algebra graph-theory matrix-decomposition share | improve this question
Read more