The following reply was made to PR pkg/32800; it has been noted by GNATS.

From: dholland@eecs.harvard.edu (David Holland)
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: pkg/32800: wine can't create ~/.wine
Date: Sun, 12 Feb 2006 01:42:58 -0500 (EST)

 (This doesn't seem to have gone through the first time)
 
 Ok, it's almost certainly at least in part a signal-handling problem.
 ktrace says:
 
  16869      1 wine     CALL  __sigprocmask14(0,0,0x7f601480)
  16869      1 wine     RET   __sigprocmask14 0
  16869      1 wine     CALL  __sysctl(0x7fc5f500,2,0x7fc5f4f8,0x7fc5f4fc,0,0)
  16869      1 wine     RET   __sysctl 0
  16869      1 wine     CALL  getpid
  16869      1 wine     RET   getpid 16869/0x41e5
  16869      1 wine     CALL  kill(0x41e5, SIGABRT)
  16869      1 wine     RET   kill 0
  16869      1 wine     PSIG  SIGABRT caught handler=0x7ffdc9d4 mask=())
  16869      1 wine     CALL  setcontext(0x7fe87cf8)
  16869      1 wine     RET   setcontext JUSTRETURN
  16869      1 wine     PSIG  SIGSEGV caught handler=0x7ffdc6dc mask=():
    code=SEGV_ACCERR, addr=0x41f5, trap=6)
  16869      1 wine     CALL  setcontext(0x7fe87cf8)
  16869      1 wine     RET   setcontext JUSTRETURN
  16869      1 wine     PSIG  SIGSEGV caught handler=0x7ffdc6dc mask=(): 
    code=SEGV_ACCERR, addr=0x41e5, trap=6)
  16869      1 wine     CALL  setcontext(0x7fe87cf8)
  16869      1 wine     RET   setcontext JUSTRETURN
  16869      1 wine     PSIG  SIGSEGV caught handler=0x7ffdc6dc mask=():
    code=SEGV_ACCERR, addr=0x41e5, trap=6)
 
 (and it continues in this fashion until killed)
 
 It's very suggestive that it seems to be trying to dereference its
 pid.
 
 This doesn't explain why it seems to have called abort(), but maybe
 that will become clear after the signal handling's straightened out.
 
 -- 
    - David A. Holland / dholland@eecs.harvard.edu