On Sunday 19 July 2009 00:47:29 Garrett Cooper wrote: > On Wed, Jul 15, 2009 at 5:37 PM, Wei Yongjun<[email protected]> wrote: > > The system call number is depend on the system architecture, not always > > 252. This patch fixed the problem. > > > > --- a/testcases/kernel/syscalls/exit_group/exit_group01.c > > - TEST(syscall(252,4)); > > + TEST(syscall(__NR_exit_group,4)); > > The best way to do this (IMHO) may be to add the relevant syscall > number to the architecture specific .in file in > testcases/kernel/include. Do you have the syscall number for your > architecture?
both should be done. syscall() should never be used with a hardcoded #. -mike
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge
_______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
