[Bug 119] malloc(0) causes portability problems (at least with AIX)

[email protected] Wed, 15 Jun 2005 12:51:18 -0400
Newsgroups gmane.comp.java.vm.sablevm.bugs
Message-ID <[email protected]>
http://sablevm.org/bugs/show_bug.cgi?id=119





------- Additional Comments From [email protected]  2005-06-15 12:51 -------
I've tested the behaviour on the AIX box we have here (running AIX 5.2). 

It is possible to access (read) location zero, but not to write to it. It does seem to contain zero. Attempting 
to write to location zero results in a segmentation fault. It's not clear that this behaviour is the same on all 
versions of AIX, and I am suspicious that it is not. Unfortunately I have only this one available for testing.

The reason for the initial report is related to the testing included in classpath's autoconf etc. There are 
(were?) problems with AIX implementation of malloc with regard to requesting a zer0-length string. I 
realize that sablevm never requests this but it would be possible in classpath's native support code, so I 
guess this is why classpath's authors included the test. My original patch was to suply the support routine 
which the auto* test was expecting.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the QA contact for the bug, or are watching the QA contact.