News for hackers. Stuff that matters.

A comment on On libunwind and dynamically generated code on x86-64. Parent comment

Re:On libunwind and dynamically generated code on x86-64 by wolfgke on Tuesday April 12, 2016 @09:39AM (#11479437)
To me this all looks like stuff that is undefined behavior in C++, so a C++ program for which such a problem occurs is by definition invalid. In other words: You have a large problem in your code.
[ Parent | on HN ]
Re:On libunwind and dynamically generated code on x86-64 by pjc50 on Tuesday April 12, 2016 @10:44AM (#11479977)
Like I said: it's crash logging code, to be used for detecting problems in the code. Undefined behaviour is not invalid: if C++ compilers rejected all UB it would be considerably easier to ship (harder to write!) reliable programs.
[ Parent | on HN ]
Re:On libunwind and dynamically generated code on x86-64 by wolfgke on Tuesday April 12, 2016 @11:15AM (#11480256)
No: The C++ standard requires from programmer that it will not trigger UB. This is a kind of contract between the programmer and the compiler.
[ Parent | on HN ]
Re:On libunwind and dynamically generated code on x86-64 by zvrba on Wednesday April 13, 2016 @01:26AM (#11485954)
The compiler vendor is free to extend the standard and define UB.
[ Parent | on HN ]