Mail Archives: djgpp/1997/04/09/09:12:55
Gruess Euch!
Eli Zaretskii wrote:
> The most probable cause is that you are dereferencing a pointer into
> an uninitialized memory. After a reboot, most of memory is zeroed,
> but after you run a compiler, it contains random values which are left
> over from the compiler run.
All my pointers are allocated with the new[] operation. It's a c++
programm.
But perhaps I do something wrong, I don't now.
> You should debug your program near the point where it crashes to find
> the exact reason. The register listing and the stack traceback
> printed when the program crashes are the point to begin your
> debugging. Use the `symify' program (described in section 9.2 of the
> DJGPP FAQ list) to translate those numbers into a human-readable
> stuff.
I've also tried this and saw that it mostly crashed after compiling
when envoking a container-template.
My solution (after "some" hours) : I've changed the Paramters of cwsdpmi
These are now:
Full name of paging file ("" to disable) ? [c:\cwsdpmi.swp]
Number of page tables to initially allocate (0=auto) ? [0]
Minimum application memory desired before 640K paging ? [432Kb]
Paragraphs of DOS memory to reserve when 640K paging ? [3840]
Paragraphs of memory for extra CWSDPMI internal heap ? [16192]
(Stil under windows I can't compile it and run it afterwards, originally
I develop
my project under OS/2 W4, which never did complain)
Now I can compile it again, but when using the -O3 switch the compiler
says
"virtual memory exhausted" at the line where the template should be
compiled. -
which doesn't bother me- not now.
Michi
--
**********************************************
Michael Schuster
E-mail: Schuster AT eev DOT e-technik DOT uni-erlangen DOT de
Lehrstuhl fuer Elektrische Energieversorgung
http://www.eev.e-technik.uni-erlangen.de/
- Raw text -