I have programs built on a large library (Cernlib), which is mostly in
fortran but has some C routines as well. It has been patched so that it
works on i386 and x86_64 machines, and with the g77 or the gfortran
compilers, through SuSE 10.2. It has drastic problems with SuSE 10.3.
As a test, I have a very simple program that calls 3 initialization
routines from the library. If the third routine is not included in the
compilation, the execution appears to be fine. But if it is included,
even if there are branch statements to avoid calling it, the code
segfaults *even before* the first two subroutines are called. I have
looked as strace and valgrind, and it is clear that the failure is
somewhere in the loading/start-up phase.
The problem occurs for 32-bit or 64-bit compilations. It occurs with
gcc/gfortran 4.1, 4.2, and 4.3 on SuSE 10.3, but not on previous SuSE
versions. An executable (static) made under SuSE 10.2 will run without
failure with SuSE 10.3, but a working one can not be generated with it.
I submitted the problem in early March to the main list and to this
list. More details can be found in this mailing list for March 6-10.
Please help. My question is: what changes were made in the system or
libraries between 10.2 and 10.3 that could produce this failure? If
this list is not the right one, where should the problem be reported to
get some attention?
Thank you.
Joe Comfort
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-programming+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-programming+help(a)opensuse.org
