DragonFly BSD
DragonFly kernel List (threaded) for 2004-03
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: coredump from linux binaries?


To: Rahul Siddharthan <rsidd@xxxxxxxxx>
From: Kip Macy <kmacy@xxxxxxxxxxx>
Date: Tue, 9 Mar 2004 00:18:24 -0800

I submitted a patch months ago to fix this. I think it probably got
dropped.

Either you or one of the committers can just go and pull the equivalent
from FreeBSD. It is a small change.


				-Kip



On Tue, 9 Mar 2004, Rahul Siddharthan wrote:

> When I do a ktrace on a coredumping linux binary as suggested
> by Kip Macy (ktrace /compat/linux/bin/sh), I get
>
>  82769 bash     CALL  ioctl(0xff,0x5410 ,0xbfbff6d4)
>  82769 bash     RET   ioctl 0
>  82769 bash     CALL  #175(0x2,0xbfbff6f0,0,0x8)
>  82769 bash     RET   #175 0
>  82769 bash     CALL  symlink(0,0x14351)
>  82769 bash     RET   symlink 0
>  82769 bash     CALL  openbsd_poll
>  82769 bash     PSIG  SIGSYS SIG_DFL
>  82769 bash     NAMI  "bash.core"
>
> The same CALL openbsd_poll just before SIGSYS when I ktrace
> /compat/linux/bin/ls, etc.  Is that syscall number (252) clashing
> with something in linux?
>
> Hm, looking into sys/syscall.h in linux (which references
> asm/unistd.h), #252 is __NR_exit_group
>
> Any ideas?
>
> Rahul
>



[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]