Hello,

Yesterday I upgraded my i386 boxes to the latest 1.5_alpha2 branch
(sources
checked out on October the 3rd). Now cvsup (netbsd a.out) fails with 

#cvsup -g -L2 /etc/supfiles/netbsd-supfile
Parsing supfile "/etc/supfiles/netbsd-supfile"

***
*** runtime error:
***    Value out of range
***    file
"/home/jdp/pm3works/pm3-1.1.13_NetBSD/libs/libm3/src/uid/POSIX/MachineIDPosix.m3",
line 73
***

  use option @M3stackdump to get a stack trace
Abort (core dumped)

I don't know it the stack trace is of any use 
------------------ EXCEPTION HANDLER STACK ---------------------
0xbfbfcfc8 RAISES {}
0xbfbfd1a8 RAISES {}
0xbfbfd21c LOCK  mutex = 0x2a62e4
0xbfbfd228 RAISES {}
0xbfbfd298 RAISES {}
0xbfbfd40c TRY-FINALLY  proc = 0x259fc   frame = 0xbfbfd650
0xbfbfd46c TRY-EXCEPT  {Main.Error}
0xbfbfd508 TRY-EXCEPT  {Thread.Alerted}
----------------------------------------------------------------


This has worked with sources from September, the 21st. 


here is the interesting part of the ktrace:

   574 cvsup    CALL  getpid
   574 cvsup    RET   getpid 574/0x23e
   574 cvsup    CALL  socket(0x1,0x1,0)
   574 cvsup    RET   socket 3
   574 cvsup    CALL  ioctl(0x3,OSIOCGIFCONF,0xbfbfd008)
   574 cvsup    RET   ioctl 0
   574 cvsup    CALL  ioctl(0x3,_IOWR('i',0x1c,0x1c),0xbfbfd170)
   574 cvsup    RET   ioctl -1 errno 45 Operation not supported
   574 cvsup    CALL  ioctl(0x3,_IOWR('i',0x1c,0x1c),0xbfbfd170)
   574 cvsup    RET   ioctl -1 errno 45 Operation not supported
   574 cvsup    CALL  ioctl(0x3,_IOWR('i',0x1c,0x1c),0xbfbfd170)
   574 cvsup    RET   ioctl -1 errno 45 Operation not supported
   574 cvsup    CALL  ioctl(0x3,_IOWR('i',0x1c,0x1c),0xbfbfd170)
   574 cvsup    RET   ioctl -1 errno 45 Operation not supported
   574 cvsup    CALL  ioctl(0x3,_IOWR('i',0x1c,0x1c),0xbfbfd170)
   574 cvsup    RET   ioctl -1 errno 45 Operation not supported
   574 cvsup    CALL  ioctl(0x3,_IOWR('i',0x1c,0x1c),0xbfbfd170)
   574 cvsup    RET   ioctl -1 errno 45 Operation not supported
   574 cvsup    CALL  ioctl(0x3,_IOWR('i',0x1c,0x1c),0xbfbfd170)
   574 cvsup    RET   ioctl -1 errno 45 Operation not supported
   574 cvsup    CALL  ioctl(0x3,_IOWR('i',0x1c,0x1c),0xbfbfd170)
   574 cvsup    RET   ioctl -1 errno 45 Operation not supported
   574 cvsup    CALL  ioctl(0x3,_IOWR('i',0x1c,0x1c),0xbfbfd170)
   574 cvsup    RET   ioctl -1 errno 45 Operation not supported
   574 cvsup    CALL  ioctl(0x3,_IOWR('i',0x1c,0x1c),0xbfbfd170)
   574 cvsup    RET   ioctl -1 errno 45 Operation not supported
   574 cvsup    CALL  ioctl(0x3,_IOWR('i',0x1c,0x1c),0xbfbfd170)
   574 cvsup    RET   ioctl -1 errno 45 Operation not supported
   574 cvsup    CALL  write(0x2,0x281ed4,0x9f)
   574 cvsup    GIO   fd 2 wrote 159 bytes
       "
        
        ***
        *** runtime error:
        ***    Value out of range



cvsup is the only  a.out binary I have on this machine...does anyone
have problems with the a.out compatibility  running a recent 1.5_alpha2
build ?

Booting the 12 days older kernel everything works fine.

--
Markus Kurek