RE: SIGSEGV in T.mprotect_P 8

>I'm working on LSB compliance for DCC, and am having a weird problem.
>Research has indicated that others have encountered the 
>problem as well,
>so it sounds like a possible TSD, but I thought I'd get your opinion.
>
>The test is /tset/LSB.os/mprotect/mprotect_P/T.mprotect_P 8, in
>lsb-runtime-test.  The test hangs; you have to kill it to continue the
>test, and it comes up UNREPORTED in the journal.  Attaching strace to
>the running test after about 30 seconds shows an endless cascade of
>SIGSEGVs.
>
>I've collected a few references to the problem occurring 
>occasionally on
>Debian, on a few architectures on the LSB Sample Implementation, and
>other random places.  In particular, this post by Mats:
>
>http://mail.freestandards.org/pipermail/lsb-test/2004-July/002710.html
>
>led me to figure out something of what's happening.

Thanks. I haven't had a chance to study in detail, but see also:
http://bugs.linuxbase.org/show_bug.cgi?id=1068
http://bugs.linuxbase.org/show_bug.cgi?id=684

for more in this area.