Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: does anyone else get a core dump from ldconfig when booting amd64-current?



In article <20090125012631.GA84416%medusa.sis.pasteur.fr@localhost>,
Nicolas Joly  <njoly%pasteur.fr@localhost> wrote:
>On Sun, Jan 25, 2009 at 12:45:14AM +0000, Christos Zoulas wrote:
>> In article <20090124235226.GA83855%medusa.sis.pasteur.fr@localhost>,
>> Nicolas Joly  <njoly%pasteur.fr@localhost> wrote:
>> >
>> >I do see similar behaviour with every -current 32-bit binaries,
>> >compiled with `cc -m32', on my up-to-date amd64 machine.
>> >
>> >njoly@lanfeust [~]> echo "int main() { return 0; }" >dummy.c
>> >njoly@lanfeust [~]> cc -m32 -o dummy dummy.c 
>> >njoly@lanfeust [~]> file ./dummy
>> >dummy: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
>> >dynamically linked (uses shared libs), for NetBSD 5.99.7, not stripped
>> >njoly@lanfeust [~]> ./dummy 
>> >zsh: bus error (core dumped)  ./dummy
>> >njoly@lanfeust [~]> echo $?
>> >138
>[...]
>> Must be a compat_netbsd32 issue with the time_t changes. ktrace might
>> help.
>
>It crash while trying to load libc.so ...
>
>njoly@lanfeust [~]> ktrace -di ./dummy
>zsh: bus error (core dumped)  ktrace -di ./dummy
>[...]
>   521      1 dummy    CALL  netbsd32_open(0xffffd490,0,0)
>   521      1 dummy    NAMI  "/emul/netbsd32/usr/lib/i386/libc.so.12"
>   521      1 dummy    NAMI  "/usr/lib/i386/libc.so.12"
>   521      1 dummy    RET   netbsd32_open 3
>   521      1 dummy    CALL  netbsd32___fstat50(3,0xffffd3d0)
>   521      1 dummy    RET   netbsd32___fstat50 0
>   521      1 dummy    CALL  netbsd32_close(3)
>   521      1 dummy    RET   netbsd32_close 0
>   521      1 dummy    PSIG  SIGBUS SIG_DFL: code=SI_USER sent by
>pid=-67194868, uid=0)
>   521      1 dummy    NAMI  "dummy.core"

Yes, I saw this. My theory is that the information that it gets from
stat is broken, and it does not load libc, but instead closes the fd.
I found the bug in the stat conversion and I committed a fix but I
doubt that this is the problem.

christos



Home | Main Index | Thread Index | Old Index