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

http://sablevm.org/bugs/show_bug.cgi?id=119

[email protected] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |
            Summary|Patches for AIX             |malloc(0) causes portability
                   |compatibility               |problems (at least with AIX)



------- Additional Comments From [email protected]  2005-06-12 01:00 -------
The memory allocations from Java side are done via 'new' and an object (even
and 0-length array) is never 0-bytes big.  This leaves us the mallocs made
from within SableVM (and possibly class library).  Yes, a C backtrace would
be most useful.

Actually I believe that with Electric Fence we should be able to catch it
even on x86.  On AIX I imagine you'd be able to either run SableVM under gdb
and get a backtrace when malloc(0) fails (I imagine it generates a signal,
like SIGSEGV?) or let it dump core and then get the backtrace from it.

I am reopening and retitling this bugreport to track this issue futher.




------- 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.