frotz@drivax.UUCP (Frotz) (10/11/89)
Has anyone seen this type of operation with Turbo C 2.0
malloc(). I am running along allocating memory and occasionally
malloc() returns a pointer to a block of memory that doesn't exist.
This certainly feels like I am stomping on malloc()'s magic, but I
have been unable to track it down. (I have a request out for a
malloc() debug package that might help). I typically get a pointer to
segment E000... Is this just me?? Details provided below.
advTHANKSance
--
Frotz
----------------------------------------------------------------------
Computer Name: IBM/PC-AT (DeltAGold Premier 386/16)
Operating System: DOS 3.20
Built-in BIOS dated: Tuesday, April 15, 1986 (Award 386 BIOS 1.1)
Main Processor: Intel 80386 Serial Ports: 2
Co-Processor: None Parallel Ports: 2
Video Display Adapter: Enhanced Graphics, 256 K-bytes
Current Video Mode: Text, 80 x 25 Color
Available Disk Drives: 20, A: - I:, P: - Z:
DOS reports 640 K-bytes of memory:
126 K-bytes used by DOS and resident programs
514 K-bytes available for application programs
A search for active memory finds:
640 K-bytes main memory (at hex 00000-0A000)
32 K-bytes display memory (at hex 0B800-0C000)
2,304 K-bytes extended memory (at hex 10000-34000)
ROM-BIOS Extensions are found at hex paragraphs: C000
Computing Index (CI), relative to IBM/XT: 16.9
Disk Index (DI), relative to IBM/XT: 2.7
Performance Index (PI), relative to IBM/XT: 12.1