GCC update to another version
by selfprogrammed from LinuxQuestions.org on (#6J6YQ)
I have got to the point where I am questioning the bug-iness of the gcc 11.2 distributed with Slackware 15.0.
There is this very large program that is very buggy. It should not be that buggy.
I have been working on it for months trying to diagnose the problem.
I have made changes like:
Code:// constructor
obj2::obj2(): ptr1(NULL), bval(false), ptr2(NULL) { }
// I changed that to:
obj2::obj2() {
ptr1 = NULL;
ptr2 = NULL;
bval = false;
}This has cured that particular bug.
I can find no reasoning for why that should make a difference, but it definitely has worked.
The program previously would crash every couple of hours, taking work with it, and has stopped doing that entirely. I have made numerous other patches, instrumentation, and other changes, that have not affected these problems at all. It is not a matter of just recompiling.
In another place I have made another change like this, with it having notable effect upon that program bug.
Did not fix it entirely, but it is like a different bug now.
Still have a mass of other bug-iness that also defies understanding.
That style of constructor is all over the program, and it is large.
// ----
I am compiling for target i686 (am running a Quad Athlon).
The program uses CMake.
I ran a memory tester for an entire night, and got no errors.
// ----
This is gcc 11.2.
A year ago, they released gcc 11.4 a bug fix release.
Any chance that gcc 11.4 could be released as a patch upgrade for Slack 15.0.
This is a system used for business purposes, developing programs, and I cannot be testing unstable compilers. I need a stable release version of gcc. I am hoping that such an upgrade just might fix some of this bug-iness.
It is also possible that the program is just that bad, or that style of constructor has those kind of problems. But I cannot find any evidence of that either.
Have compiled a massive amount of slackbuilds using this compiler, and have not noticed anything like this with other programs. So I am confused. Getting desperate to try something, and upgrading GCC is a way to test if that makes a difference.
Trying to put another GCC on the side, and getting this slackbuild to compile with that does not look like an easy task.
There is this very large program that is very buggy. It should not be that buggy.
I have been working on it for months trying to diagnose the problem.
I have made changes like:
Code:// constructor
obj2::obj2(): ptr1(NULL), bval(false), ptr2(NULL) { }
// I changed that to:
obj2::obj2() {
ptr1 = NULL;
ptr2 = NULL;
bval = false;
}This has cured that particular bug.
I can find no reasoning for why that should make a difference, but it definitely has worked.
The program previously would crash every couple of hours, taking work with it, and has stopped doing that entirely. I have made numerous other patches, instrumentation, and other changes, that have not affected these problems at all. It is not a matter of just recompiling.
In another place I have made another change like this, with it having notable effect upon that program bug.
Did not fix it entirely, but it is like a different bug now.
Still have a mass of other bug-iness that also defies understanding.
That style of constructor is all over the program, and it is large.
// ----
I am compiling for target i686 (am running a Quad Athlon).
The program uses CMake.
I ran a memory tester for an entire night, and got no errors.
// ----
This is gcc 11.2.
A year ago, they released gcc 11.4 a bug fix release.
Any chance that gcc 11.4 could be released as a patch upgrade for Slack 15.0.
This is a system used for business purposes, developing programs, and I cannot be testing unstable compilers. I need a stable release version of gcc. I am hoping that such an upgrade just might fix some of this bug-iness.
It is also possible that the program is just that bad, or that style of constructor has those kind of problems. But I cannot find any evidence of that either.
Have compiled a massive amount of slackbuilds using this compiler, and have not noticed anything like this with other programs. So I am confused. Getting desperate to try something, and upgrading GCC is a way to test if that makes a difference.
Trying to put another GCC on the side, and getting this slackbuild to compile with that does not look like an easy task.