This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libc/11865] SegFault in libc_print_version on program start


------- Additional Comments From beartham at gmail dot com  2010-07-31 21:15 -------
Subject: Re:  SegFault in libc_print_version on program start

On Sat, Jul 31, 2010 at 3:11 PM, Joseph Thames <beartham@gmail.com> wrote:
>
> Originally this problem was showing up following static linking of a fortran program (two cases, one using a g77 compiler and the other using the gfortran compiler) as a "bad ELF interpreter, no such file or directory" message, followed by a "success" message(???). We determined that the file it was looking for was libc.so.1.? So I symbolic linked /usr/lib/libc.so.1 to /lib/libc-2.5.so, and when I reran the executable, I got the segfault in version.c, when it was trying to print the GNU version banner. So it is definitely a problem in the C library.
>
> I had used the small Fortran program in place of the large Fortran program that originally produced the segfault, to eliminate the possibility that it might have been the linking of the large program from a set of external libraries (overwriting a pointer, etc.) that caused the problem. The little Fortran program did not link anything from these libraries, but it produced the segfault.
>
> So far I have not been able to get any Fortran programs to execute after loading, because of this libc segfault.? I have downloaded glibc source and have commented out the call to _libc_print_version in version.c.? I'm getting ready to recompile and test this modified glibc, so I can get my Fortran programs to execute. I will let you know the results.
>
> Best regards,
>
> Joseph Thames
>
> On Sat, Jul 31, 2010 at 12:17 PM, drepper at redhat dot com <sourceware-bugzilla@sourceware.org> wrote:
>>
>> ------- Additional Comments From drepper at redhat dot com ?2010-07-31 18:17 -------
>> If you cannot reproduce a problem with a valid C program it is no problem in the
>> C library. ?Don't submit Fortran code.
>>
>> --
>> ? ? ? ? ? What ? ?|Removed ? ? ? ? ? ? ? ? ? ? |Added
>> ----------------------------------------------------------------------------
>> ? ? ? ? ? ? Status|NEW ? ? ? ? ? ? ? ? ? ? ? ? |WAITING
>>
>>
>> http://sourceware.org/bugzilla/show_bug.cgi?id=11865
>>
>> ------- You are receiving this mail because: -------
>> You reported the bug, or are watching the reporter.
>
>
>
> --
> Joseph 'Bear' Thames
> MetaCalculus, LLC and Meta Science Foundation
> (505) 977-9024 - Cell Phone
> beartham@gmail.com



--
Joseph 'Bear' Thames
MetaCalculus, LLC and Meta Science Foundation
(505) 977-9024 - Cell Phone
beartham@gmail.com

------- Additional Comments From drepper at redhat dot com  2010-07-31 21:22 -------
> Originally this problem was showing up following static linking of a fortran
program
> (two cases, one using a g77 compiler and the other using the gfortran
compiler) as a
> "bad ELF interpreter, no such file or directory" message, followed by a "success"
> message(???). We determined that the file it was looking for was libc.so.1.  So I
> symbolic linked /usr/lib/libc.so.1 to /lib/libc-2.5.so, and when I reran the
> executable, I got the segfault in version.c, when it was trying to print the GNU
> version banner. So it is definitely a problem in the C library.
>
> I had used the small Fortran program in place of the large Fortran program that
> originally produced the segfault, to eliminate the possibility that it might
have been
> the linking of the large program from a set of external libraries (overwriting a
> pointer, etc.) that caused the problem. The little Fortran program did not link
> anything from these libraries, but it produced the segfault.
>
> So far I have not been able to get any Fortran programs to execute after loading,
> because of this libc segfault.  I have downloaded glibc source and have
commented out
> the call to _libc_print_version in version.c.  I'm getting ready to recompile
and test
> this modified glibc, so I can get my Fortran programs to execute. I will let
you know
> the results.


Obviously broken environment coupled with completely incorrect sysadmin work. 
libc.so.1 has nothing whatsoever to do with glibc so what do you ecpect?

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
         Resolution|                            |INVALID


http://sourceware.org/bugzilla/show_bug.cgi?id=11865

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]