Re: Linux emulation problem

To: Nicolas Joly <njoly%pasteur.fr@localhost>
Subject: Re: Linux emulation problem
From: Torsten Harenberg <harenberg%physik.uni-wuppertal.de@localhost>
Date: Tue, 28 Jun 2011 23:17:25 +0200

Hi Nicolas,

Am 28.06.2011 um 22:55 schrieb Nicolas Joly:

> 
> Looks like something similar a problem i currently see on my machines
> with forked processes crashing.
> 
> njoly@lanfeust [~]> ktrace -di ./fork64
> fork64: child failed
> njoly@lanfeust [~]> kdump
> [...]
> 15032  15032 fork64   CALL  clone(0x1200011,0,0,0x68e8e0,0)
> 15032  15032 fork64   RET   clone 8516/0x2144
> 15032  15032 fork64   CALL  wait4(0xffffffffffffffff,0x7f7ffffff16c,0,0)
>  8516   8516 fork64   EMUL  "linux"
>  8516   8516 fork64   RET   fork 0
>  8516   8516 fork64   PSIG  SIGSEGV SIG_DFL: 
> code=SEGV_MAPERR,addr=0x90,trap=14)
>  8516   8516 fork64   NAMI  "fork64.core"
> 15032  15032 fork64   RET   wait4 8516/0x2144
> 
> Can you try the attached forked binary, compiled on CentOS 5.6 x86_64
> machine from given fork.c source.


I compiled it myself on one of my CentOS 5.5 machines (haven't upgraded yet) 
and tried this one plus the binary you had and the output looks :

[23:11] harenber@charm:~ $ gcc -static -o fork64_CentOS5.5_static fork.c 
[23:07] harenber@charm:~ $ ./fork64_CentOS5.5 
[23:07] harenber@charm:~ $ cat /etc/issue
CentOS release 5.5 (Final)
Kernel \r on an \m





mail# ktrace -di ./fork64_CentOS5.5_static                                     
linux_probe: returning 0
fork64_CentOS5.5_static: child failed
mail# kdump
  1486      1 ktrace   EMUL  "netbsd"
  1486      1 ktrace   RET   ktrace 0
  1486      1 ktrace   CALL  
execve(0x7f7ffffffe3b,0x7f7fffffdc88,0x7f7fffffdc98)
  1486      1 ktrace   NAMI  "./fork64_CentOS5.5_static"
  1486      1 fork64_CentOS5.5 NAMI  "/emul/linux"
  1486   1486 fork64_CentOS5.5 EMUL  "linux"
  1486   1486 fork64_CentOS5.5 RET   syscall -1 errno -2 No such file or 
directory
  1486   1486 fork64_CentOS5.5 CALL  uname(0x7f7ffffff2d0)
  1486   1486 fork64_CentOS5.5 RET   uname 0
  1486   1486 fork64_CentOS5.5 CALL  brk(0)
  1486   1486 fork64_CentOS5.5 RET   brk 6873088/0x68e000
  1486   1486 fork64_CentOS5.5 CALL  brk(0x68ef20)
  1486   1486 fork64_CentOS5.5 RET   brk 6877184/0x68f000
  1486   1486 fork64_CentOS5.5 CALL  arch_prctl(0x1002,0x68e850)
  1486   1486 fork64_CentOS5.5 RET   arch_prctl 0
  1486   1486 fork64_CentOS5.5 CALL  brk(0x6b0000)
  1486   1486 fork64_CentOS5.5 RET   brk 7012352/0x6b0000
  1486   1486 fork64_CentOS5.5 CALL  clone(0x1200011,0,0,0x68e8e0,0)
  1486   1486 fork64_CentOS5.5 RET   clone 1736/0x6c8
  1486   1486 fork64_CentOS5.5 CALL  
wait4(0xffffffffffffffff,0x7f7ffffff27c,0,0)
  1736   1736 fork64_CentOS5.5 EMUL  "linux"
  1736   1736 fork64_CentOS5.5 RET   fork 0
  1736   1736 fork64_CentOS5.5 PSIG  SIGSEGV SIG_DFL: code=SEGV_MAPERR, 
addr=0x90, trap=14)
  1736   1736 fork64_CentOS5.5 NAMI  "fork64_CentOS5.5.core"
  1486   1486 fork64_CentOS5.5 RET   wait4 1736/0x6c8
  1486   1486 fork64_CentOS5.5 CALL  write(2,0x7f7fffffc8b0,0x19)
  1486   1486 fork64_CentOS5.5 GIO   fd 2 wrote 25 bytes
       "fork64_CentOS5.5_static: "
  1486   1486 fork64_CentOS5.5 RET   write 25/0x19
  1486   1486 fork64_CentOS5.5 CALL  write(2,0x7f7fffffc990,0xc)
  1486   1486 fork64_CentOS5.5 GIO   fd 2 wrote 12 bytes
       "child failed"
  1486   1486 fork64_CentOS5.5 RET   write 12/0xc
  1486   1486 fork64_CentOS5.5 CALL  write(2,0x68a543,1)
  1486   1486 fork64_CentOS5.5 GIO   fd 2 wrote 1 bytes
       "\n"
  1486   1486 fork64_CentOS5.5 RET   write 1
  1486   1486 fork64_CentOS5.5 CALL  exit_group(1)
mail# 
mail# ktrace -di ./fork64                                                      
linux_probe: returning 0
fork64: child failed
mail# kdump
  1442      1 ktrace   EMUL  "netbsd"
  1442      1 ktrace   RET   ktrace 0
  1442      1 ktrace   CALL  
execve(0x7f7ffffffe4b,0x7f7fffffdc98,0x7f7fffffdca8)
  1442      1 ktrace   NAMI  "./fork64"
  1442      1 fork64   NAMI  "/emul/linux"
  1442   1442 fork64   EMUL  "linux"
  1442   1442 fork64   RET   syscall -1 errno -2 No such file or directory
  1442   1442 fork64   CALL  uname(0x7f7ffffff2e0)
  1442   1442 fork64   RET   uname 0
  1442   1442 fork64   CALL  brk(0)
  1442   1442 fork64   RET   brk 6873088/0x68e000
  1442   1442 fork64   CALL  brk(0x68ef20)
  1442   1442 fork64   RET   brk 6877184/0x68f000
  1442   1442 fork64   CALL  arch_prctl(0x1002,0x68e850)
  1442   1442 fork64   RET   arch_prctl 0
  1442   1442 fork64   CALL  brk(0x6b0000)
  1442   1442 fork64   RET   brk 7012352/0x6b0000
  1442   1442 fork64   CALL  clone(0x1200011,0,0,0x68e8e0,0)
  1442   1442 fork64   RET   clone 1070/0x42e
  1442   1442 fork64   CALL  wait4(0xffffffffffffffff,0x7f7ffffff28c,0,0)
  1070   1070 fork64   EMUL  "linux"
  1070   1070 fork64   RET   fork 0
  1070   1070 fork64   PSIG  SIGSEGV SIG_DFL: code=SEGV_MAPERR, addr=0x90, 
trap=14)
  1070   1070 fork64   NAMI  "fork64.core"
  1442   1442 fork64   RET   wait4 1070/0x42e
  1442   1442 fork64   CALL  write(2,0x7f7fffffc8c0,8)
  1442   1442 fork64   GIO   fd 2 wrote 8 bytes
       "fork64: "
  1442   1442 fork64   RET   write 8
  1442   1442 fork64   CALL  write(2,0x7f7fffffc9a0,0xc)
  1442   1442 fork64   GIO   fd 2 wrote 12 bytes
       "child failed"
  1442   1442 fork64   RET   write 12/0xc
  1442   1442 fork64   CALL  write(2,0x68a543,1)
  1442   1442 fork64   GIO   fd 2 wrote 1 bytes
       "\n"
  1442   1442 fork64   RET   write 1
  1442   1442 fork64   CALL  exit_group(1)

So.. yes, looks like it also appears here.

BTW: I have 

mail# pkg_info -a | grep suse
suse_base-10.0nb5   Linux compatibility package
suse_aspell-10.0nb2 Linux compatibility package for aspell
suse_compat-10.0nb3 Linux compatibility package with old shared libraries
suse_openssl-10.0nb5 Linux compatibility package for OpenSSL
suse_libcups-10.0nb4 Linux compatibility package for CUPS
suse_expat-10.0nb2  Linux compatibility package for expat
suse_freetype2-10.0nb5 Linux compatibility package for freetype-2.x
suse_fontconfig-10.0nb7 Linux compatibility package for fontconfig
suse_x11-10.0nb4    Linux compatibility package for X11
suse_gtk-10.0nb2    Linux compatibility package for GTK+-1.x
suse_gdk-pixbuf-10.0nb3 Linux compatibility package for gdk-pixbuf
suse_glx-10.0nb4    Linux compatibility package for OpenGL/Mesa
suse_libjpeg-10.0nb2 Linux compatibility package for JPEG
suse_libpng-10.0nb4 Linux compatibility package for PNG
suse-10.0nb4        SUSE-based Linux binary emulation environment
suse_libtiff-10.0nb4 Linux compatibility package for TIFF
suse_gtk2-10.0nb4   Linux compatibility package for GTK+-2.x
suse_locale-10.0nb2 Linux compatibility package with locale files
suse_openmotif-10.0nb2 Linux compatibility package for OpenMotif
suse_slang-10.0nb3  Linux compatibility package for S-Lang
suse_vmware-10.0nb2 Linux compatibility package to help run VMware
suse_libxml2-10.0nb2 Linux compatibility package for libxml2

at the moment.

Best regards,

   Torsten

--
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
<>                                                              <>
<> Dr. Torsten Harenberg     harenberg%physik.uni-wuppertal.de@localhost  <>
<> Bergische Universitaet                                       <>
<> FB C - Physik             Tel.: +49 (0)202 439-3521          <>
<> Gaussstr. 20              Fax : +49 (0)202 439-2811          <>
<> 42097 Wuppertal                                              <>
<>                                                              <>
<><><><><><><>< Of course it runs NetBSD http://www.netbsd.org ><>

Follow-Ups:
- Re: Linux emulation problem
  - From: Christos Zoulas
- Re: Linux emulation problem
  - From: Nicolas Joly

References:
- Linux emulation problem
  - From: Torsten Harenberg
- Re: Linux emulation problem
  - From: Christos Zoulas
- Re: Linux emulation problem
  - From: Torsten Harenberg
- Re: Linux emulation problem
  - From: Christos Zoulas
- Re: Linux emulation problem
  - From: Torsten Harenberg
- Re: Linux emulation problem
  - From: Nicolas Joly

Prev by Date: Re: Linux emulation problem
Next by Date: Re: Linux emulation problem
Previous by Thread: Re: Linux emulation problem
Next by Thread: Re: Linux emulation problem
Indexes:

Home | Main Index | Thread Index | Old Index