Re: [Mingw-msys] Win32 error 487

[Prof A O. (T. A. Chief) <chi...@bi...>]

On 22 May 2004 at 13:03, Earnie Boyd wrote:

[...]
> So, set a filter to exclude rxvt from the output.  Or use the --norxvt
> switch to msys.bat (assuming you're using the most recent version of
> msys.bat).  Or set a filter for DbgView to display only the data that
> may be from cygheap.cc.  Lot's of  methods.  Then there is the gdb
> method.  And there's ``objdump -Sd msys-1.0.dll > /tmp/odmp'' to help as
> well.  Also ``strace -o /tmp/strace.out foo.exe'' may be what the doctor
> ordered.

Thanks. I did most of the above with no more illumination. Gdb simply 
reports that the process terminated with code 01. Strace.out has 0 
bytes. Dbgview still has loads of stuff (with "[main] sh ..." or "[sig] 
sh ..."). There's lots of lines referring to signal.cc, sigproc.cc and 
malloc.cc, but nothing relating to cygheap.cc. There's also other stuff 
about "looking for processes to reap", etc., but nothing telling me how 
the system came to decide that the program is asking for too much heap 
memory, how much that memory is, and where it happened. I am afraid 
that the debug messages are probably only intelligble to the person who 
wrote them in the first place. I suppose it is in malloc.cc that one 
should be looking, but I am not sure what I am looking for. A series of 
debug messages in the actual code for example1.exe never get displayed -
 meaning that the error happened before any code that I wrote ever gets 
executed. So, I should be looking in the startup code. 

Any clues? Thanks.

Best regards, The Chief
--------
Prof. Abimbola A. Olowofoyeku (The African Chief) 
web:  http://www.greatchief.plus.com/