On 14 Oct 2001, Nathan J. Williams wrote:
> That looks more like kdump being confused; it's reporting the system
> call entries for the wrong emulation (native NetBSD, rather than
> Linux). You might try "kdump -e linux", though it ought to figure that
> out anyway.
> 
> Is that really the end of the dump?

Almost. Using "kdump -e linux", I now get:

 16942 Winamp.exe RET   rt_sigprocmask 0
 16942 Winamp.exe CALL  rt_sigsuspend(0xbfbf912c,0x8)
 16950 Winamp.exe RET   fork 0
 16950 Winamp.exe CALL  getpid
 16950 Winamp.exe RET   getpid 16950/0x4236
 16950 Winamp.exe CALL  rt_sigprocmask(0x2,0xbf3ffea4,0,0x8)
 16950 Winamp.exe RET   rt_sigprocmask 0
 16950 Winamp.exe CALL  gettimeofday(0xbf3ffcd4,0xbf3ffcdc)
 16950 Winamp.exe RET   gettimeofday 0
 16950 Winamp.exe CALL  gettimeofday(0xbf3fecb4,0xbf3fecbc)
 16950 Winamp.exe RET   gettimeofday 0
 16950 Winamp.exe PSIG  SIGSEGV SIG_DFL 
 16950 Winamp.exe NAMI  "Winamp.exe.core"
 16949 Winamp.exe PSIG  SIGUSR2 caught handler=0x485f9d00 mask=(30) code=0x0  
 16949 Winamp.exe RET   kill 0
 16949 Winamp.exe CALL  sigreturn(0x81e2a04)
 16949 Winamp.exe RET   sigreturn -1 errno -2 No such file or directory
 16949 Winamp.exe CALL  poll(0x81e2ac0,0x1,0x7d0)
 16949 Winamp.exe RET   poll 1
 16949 Winamp.exe CALL  getppid
 16949 Winamp.exe RET   getppid 16942/0x422e
 16949 Winamp.exe CALL  wait4(0xffffffff,0x81e2a98,0x80000001,0)
 16949 Winamp.exe RET   wait4 16950/0x4236
 16949 Winamp.exe CALL  kill(0x422e,0xb)
 16942 Winamp.exe PSIG  SIGSEGV SIG_DFL
 16942 Winamp.exe NAMI  "Winamp.exe.core"
 16949 Winamp.exe RET   kill 0
 16949 Winamp.exe CALL  exit(0)

Looks like a segv in application code. ;(


 - Hubert

-- 
Want to get a clue on IPv6 but don't know where to start? Try this:
* Basics -> http://www.onlamp.com/pub/a/onlamp/2001/05/24/ipv6_tutorial.html
* Setup  -> http://www.onlamp.com/pub/a/onlamp/2001/06/01/ipv6_tutorial.html 
Of course with your #1 IPv6 ready operating system -> http://www.NetBSD.org/