Menu
▾
▴
Re: [LTP] signal() failed for signal 34.
|
From: Robert W. <ro...@us...> - 2003-11-24 17:57:12
|
How about using this:
/* Needed if __pthread_sig_debug support exists*/
#ifdef __pthread_sig_debug
case __pthread_sig_debug:
#endif
Does this work? Or must I define __pthread_sig_debug to 34....which puts us
back into the same issue.
(See attached file: tst_sig.c)
-Robbie
Robert V. Williamson <ro...@us...>
Linux Test Project
IBM Linux Technology Center
Web: http://ltp.sourceforge.net
IRC: #ltp on freenode.irc.net
====================
"Only two things are infinite, the universe and human stupidity, and I'm
not sure about the former." -Albert Einstein
Chris.Pedley@arm.
com To: Robert Williamson/Austin/IBM@IBMUS
cc: ltp...@li...
11/24/2003 10:56 Subject: Re: [LTP] signal() failed for signal 34.
AM
Hi,
I've tried this (the corrected version you sent out in the next email) and
it appears to fix the problem. It will take some time to go through all of
the system calls but I've tried the ones that were broken before and they
are now working.
However, I'm not sure that adding just the following to tst_sig is the best
solution:
/*Test for ARM */
case 34:
I'm not convinced that this is an ARM Linux specific problem. The
definition of __pthread_sig_debug (which is SIG_RTMIN+2) is not in an ARM
specific part of glibc. I think this problem will always occur on Linuxes
that have been built to have real-time signal support. I'm not sure where
this gets configured though, the kernel or glibc?
Also, __pthread_sig_debug is an internal name for linuxthreads, but
presumably it must be known by something externally. Just having 'case 34'
will undoubtedly lead to trouble somewhere along the line when the
definition of __pthread_sig_debug changes.
Any thoughts?
Chris
On 24/11/2003 16:03:42 ltp-list-admin wrote:
>This looks like a kernel/system specific conflict with tst_sig.c. We ran
>into a similar problem with NPTL, when they added SIGCANCEL(32) and
>SIGTIMER(33). Could you try using this modified version of tst_lib.c and
>let me know if it works?
>(See attached file: tst_sig.c)
>
>-Robbie
>
>Robert V. Williamson <ro...@us...>
>Linux Test Project
>IBM Linux Technology Center
>Web: http://ltp.sourceforge.net
>IRC: #ltp on freenode.irc.net
>====================
>"Only two things are infinite, the universe and human stupidity, and I'm
>not sure about the former." -Albert Einstein
>
>
>
>Chr...@ar...
>Sent by: To: ltp...@li...
>ltp...@li...ur cc:
>ceforge.net Subject: [LTP] signal() failed for
signal 34.
>
>
>11/24/2003 09:42 AM
>
>
>
>
>
>Hi,
>
>I've tried running the system calls tests from the LTP (ltp-full-20031106)
>on ARM Linux and a large number of them fail. Most of them fail with
>exactly the same error:
>WARN : signal() failed for signal 34. error:22 Invalid argument
>
>This appears to happen because lots of the tests call tst_sig from their
>setup functions. tst_sig then calls tst_setup_signal which calls
>sigaction. If linuxthreads is present then the following piece of code is
>inside the __sigaction function in glibc/linuxthreads/signals.c:
>
>if (sig == __pthread_sig_restart ||
>sig == __pthread_sig_cancel ||
>(sig == __pthread_sig_debug && __pthread_sig_debug > 0))
>{
>return -1;
>}
>
>The problem is that tst_sig tries to assign an action to a signal with the
>same number as __pthread_sig_debug. It seems that __pthread_sig_debug is
>greater than 0 as long as real-time signals are available.
>
>Anyone have any ideas on how to fix this in the test harness, and why it
>hasn't been noticed on other versions of linux with LTP?
>
>Thanks.
>
>--
>Chris Pedley, Graduate Engineer
>Intellectual Property Products Division
>ARM Ltd, 110 Fulbourn Rd, Cambridge CB1 9NJ UK
>Tel : +44 1223 400847 Fax: +44 1223 400410
>
>This e-mail message is intended for the addressee(s) only and may contain
>information that is the property of, and/or subject to a confidentiality
>agreement between the intended recipient(s), their organisation and/or the
>ARM Group of Companies. If you are not an intended recipient of this
e-mail
>message, you should not read, copy, forward or otherwise distribute or
>further disclose the information in it; misuse of the contents of this
>e-mail message may violate various laws in your state, country or
>jurisdiction. If you have received this e-mail message in error, please
>contact the originator of this e-mail message via e-mail and delete all
>copies of this message from your computer or network, thank you.
>
>
>
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: SF.net Giveback Program.
>Does SourceForge.net help you be more productive? Does it
>help you create better code? SHARE THE LOVE, and help us help
>YOU! Click Here: http://sourceforge.net/donate/
>_______________________________________________
>Ltp-list mailing list
>Ltp...@li...
>https://lists.sourceforge.net/lists/listinfo/ltp-list
>
> - tst_sig.c
--
Chris Pedley, Graduate Engineer
Intellectual Property Products Division
ARM Ltd, 110 Fulbourn Rd, Cambridge CB1 9NJ UK
Tel : +44 1223 400847 Fax: +44 1223 400410
This e-mail message is intended for the addressee(s) only and may contain
information that is the property of, and/or subject to a confidentiality
agreement between the intended recipient(s), their organisation and/or the
ARM Group of Companies. If you are not an intended recipient of this e-mail
message, you should not read, copy, forward or otherwise distribute or
further disclose the information in it; misuse of the contents of this
e-mail message may violate various laws in your state, country or
jurisdiction. If you have received this e-mail message in error, please
contact the originator of this e-mail message via e-mail and delete all
copies of this message from your computer or network, thank you.
|