> >Synopsis:       kdump dumps core on sparc64/compat_svr4
 
> and see a segfault.
> 
> In this example, the top part of the kdump output (before it dies) is:
> 
>    522 ktrace   EMUL  "netbsd"
>    522 ktrace   RET   ktrace 0
>    522 ktrace   CALL  execve(0xffffffffffffdad7,0xffffffffffffd950,0xffffffffffffd960)
>    522 ktrace   NAMI  "./hello"
>    522 hello    EMUL  "svr4_32"
>    522 hello    RET   execve JUSTRETURN
>    522 hello    CALL  ioctl(0x1,_IOWR('<D9>',0x50),0xffffffffffffd960,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,

Clearly the argument count is wrong.  kdump seems to assume that the 'ioctl'
has at least 2 arguments (will fix soon).

kdump -n should then generate a valid trace output.
I wonder if kdump understands the xxx_32 emulations at all???
Either that or the system call numbers are being decoded incorrectly.

	David

-- 
David Laight: david@l8s.co.uk