This is the mail archive of the java@gcc.gnu.org mailing list for the Java 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] | |
Citando Andrew Haley <aph@redhat.com>: > I can't reproduce this. I guess it's probably a Windows-specific thing. > > The gc calls either VirtualAlloc or GlobalAlloc, depending on how it > is configured. If either of these fails, the full error information > may be retrieved by calling GetLastError. > > If I were you, I'd go into os_dep.c and add a bunch of trace > information to GC_win32_get_mem to see why the gc is failing to > allocate memory. > > Andrew. > Took me a while, but I finally learned how to compile it... But it didn't show anything interesting, no errors. I've attached the output of the test, but the error doesn't seem to be in GC_win32_get_mem(). It calls VirtualAlloc(), but never fails... It only calls GC_win32_get_mem() a few times. The OutOfMemoryError exception is thrown from somewhere else.
Attachment:
log.txt
Description: Text document
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |