This is the mail archive of the cygwin-developers@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [Patch] Update for the testsuite, devdsp


At 11:59 AM 8/24/2004 +0200, Corinna Vinschen wrote:
>On Aug 21 15:39, Pierre A. Humblet wrote:
>> 
>> Attached are winsup.sum and winsup.log
>> 
>> There are many mmap failures (including a dump in
>> mmaptest01), I have not looked at them.
>
>I did now.  I shouldn't have.  It makes bad dreams. 
>
>mmaptest01 crashes because of this extraordinary dumb problem on 9x.
>When creating two maps using MapViewOfFile which are mapping the same
>address in the same file, the function always returns a pointer to the
>same shared region.  The testcase relies on mmap returning two different
>addresses in adjacent mmap calls.  It unmaps one of them, which results
>on 9x in munmapping both.  The following access to this memory page
>then crashes on 9x.  Since I don't see a way to workaround that in
>Cygwin, I've changed the testcase to accomodate that behaviour.
>
>The FAILs in mmaptest02 and mmaptest03 are expected FAILs since the
>tests rely on the VirtualProtect ability, which 9x doesn't have on
>shared pages.

OK, thanks. I don't want to cause you more bad dreams but there are
also 4 failing tests in the ltp/mmap series !

>> ltp/symlink01 has a SIGSEV, but I think it happens during a printf
>>  triggered by a hard link related failure.
>>  So it's either the test program or newlib. 
>
>The test program uses %d format specifiers for printing inode numbers.
>I changed the testcase to use %llu instead.

Wow, I had never realized this could cause a SIGSEGV. The testsuite is
full of such incorrect %d, not to mention almost all applications
that print inode numbers (such as exim). 

Pierre


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]