Mail Archives: djgpp/2002/03/24/11:23:16
> The failure reflected a 64K boundry on first number: "can't allocate
> 65536 bytes after allocating 7783800 bytes."
There are no 64k boundaries in DJGPP, as it is a 32-bit environment.
The fact that the error lists exactly 64k bytes is just a coincidence.
This error is most likely either (1) a program error, or (2) an out of
memory error. Since gcc uses a lot of memory when building programs,
#2 is the most likely. Run just "go32-v2" in a DOS command shell, and
it should tell you how much memory is available. In this example, the
"DPMI ... available" lines are what we're looking for:
C:\> go32-v2
go32/v2 version 2.0 built Nov 15 1998 14:36:43
Usage: go32 coff-image [args]
Rename this to go32.exe only if you need a go32 that can run v2 binaries as
well as v1 binaries (old makefiles). Put ahead of the old go32 in your PATH
but do not delete your old go32 - leave it in the PATH after this one.
Set GO32_V2_DEBUG=y in the environment to get verbose output.
DPMI memory available: 65515 Kb
DPMI swap space available: 0 Kb
If this number is close to 7783k, then FAQ section 15.6 should help
you increase it: http://www.delorie.com/djgpp/v2faq/faq15_6.html
> As for your message: Before submitting this form, ask yourself - did
> you ask this question in comp.os.msdos.djgpp or djgpp AT delorie DOT com
> first? If not, why not? You should do that, and wait for an answer,
> before using this form.
The reason is because DJGPP is itself a combination of many individual
packages that each have their own support groups, depending on what
the problem is. The form you were looking at is part of the support
structure for the djgpp runtime library, libc.a. It is not, for
example, for gcc, the debugger, or Allegro. It's also not a place to
ask for help - it's only for archiving new valid bugs in the library.
The only way to find out if it's a new valid bug is to ask on the
general djgpp mailing list.
> I'm not a user of gxx or a c++ programer. My son is. I'm hardware
> tech support ( 40+ years). You're talking greek to me. I told you,
> I'm hardware, not programmer geek.
As a tech support person, you should understand the importance of
reporting the problem to the correct place (which you did, thanks :)
Here, we will work with you (or your son) to determine what the
original cause of the problem is, and then either help you fix it or
refer you to the right place to get further support for it.
- Raw text -