This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug other/8822] internal error segmentation fault on dual-systems
- From: "dieter dot ferdinand at gmx dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 6 Dec 2003 20:31:16 -0000
- Subject: [Bug other/8822] internal error segmentation fault on dual-systems
- References: <20021205070600.8822.dieter.ferdinand@gmx.de>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From dieter dot ferdinand at gmx dot de 2003-12-06 20:31 -------
hello,
i have installed the new version last week and make some test with 2 cpu's
active.
at the first compilation, the compiler breaks some times by compiling itself.
when i boot the system as single-cpu-system, there are no problems, but when i
activate the second cpu the compiler crashs with different error-messages.
i think, that there are one ore more variables are not initialisized, when a
new thread starts, while the thread is started, before all variables are
initialized.
i will try the option --disable-hreads and hope, the threading of the compiler
self is disabled with them.
please try to compile gcc on a multiprocessor-system some times to get the same
errors.
this error comes also by compiling other big programs, but most time at an
other position of the compilation process.
i don't think, that this is a bug by my hardware (all programms runs error free
on this system, also multithreading programs. only gcc makes errors), but i
have other dual-systems, on which i can test it in next time. i use this
systems normaly under win2000 to convert video-files an this systems is stable.
there is no possibility to reproduce this error at a spezific point of a
compilation. the only way, to fix all errors, which depend on the same problem
is to check alle points, at which a new thread is started, that all variables,
which transfered to this thread are initialized.
it is also possible, that the error comes with the uses threading lib, but i
don't know, how i can check this, while all other multitreading programs, which
i used, make no problems.
i use glibc 2.3.2 and i have updated all other libs in the last 6 month to the
newest version.
goodby
--
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
Summary|internal error segmentation |internal error segmentation
|fault |fault on dual-systems
Version|3.2.1 |3.3.2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8822