Prof A Olowofoyeku (The African Chief) wrote:
>On 22 May 2004 at 6:48, Earnie Boyd wrote:
>
>[...]
>
>
>>Startup the debug version of MSYS and use strace or DbgView to debug it.
>> Caution, all process are slower; use the debug version only for
>>debugging. Caution, comparison to the Cygwin code as it exists today is
>>fruitless. Hint: Copy the desktop icon and modify the properties of the
>>copy to point to the /c/msys/debug/msys.bat and /c/msys/debug/bin
>>directories.
>>
>>I'll be looking forward to a patch.
>>
>>
>
>Hmmm ... running DbgView shows me zillions of lines of stuff - and
>there is nothing on any of them that shows me what is wrong. I can't
>even ascertain which program is producing the lines, since they all
>seem to be coming from rxvt.
>
>
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.
Earnie
--
http://www.mingw.orghttp://sourceforge.net/projects/mingwhttps://sourceforge.net/donate/index.php?user_id=15438

On 22 May 2004 at 6:48, Earnie Boyd wrote:
[...]
> Startup the debug version of MSYS and use strace or DbgView to debug it.
> Caution, all process are slower; use the debug version only for
> debugging. Caution, comparison to the Cygwin code as it exists today is
> fruitless. Hint: Copy the desktop icon and modify the properties of the
> copy to point to the /c/msys/debug/msys.bat and /c/msys/debug/bin
> directories.
>
> I'll be looking forward to a patch.
Hmmm ... running DbgView shows me zillions of lines of stuff - and
there is nothing on any of them that shows me what is wrong. I can't
even ascertain which program is producing the lines, since they all
seem to be coming from rxvt.
Best regards, The Chief
--------
Prof. Abimbola A. Olowofoyeku (The African Chief)
web: http://www.greatchief.plus.com/

On 22 May 2004 at 6:48, Earnie Boyd wrote:
[...]
> >
> I am willing to help you debug MSYS.
Thanks. I am wondering whether the problem doesn't acutally lie in the
startup code. The Cygwin threads I have followed on this topic seem to
suggest that cygheap.c might be the place to look, but I will
investigate the startup code in the runtime system first.
Best regards, The Chief
--------
Prof. Abimbola A. Olowofoyeku (The African Chief)
web: http://www.greatchief.plus.com/

Prof A Olowofoyeku (The African Chief) wrote:
> That is what the Msys system has decided - but the test program does
>
>not (at least, it is not supposed to) use much memory at all. Indeed,
>all it does is to use the functionality of a (Pascal) class library
>that I am building to create a top-level window that does nothing. I am
>not sure however how to check my use of the memory heap or how such a
>trivial program could exceed the allocated heap space (where is the
>heap space allocated, and how much is allocated?).
>
>I am trying to support all Win32 gnu platforms with this class library.
>I have checked the header flags in the executable for reserved and
>allocated stack and heap space. These are exactly the same in the
>Cygwin, Mingw, and Msys executable (as they should be), since the code
>is exactly the same, and uses the same Winapi calls. So something is
>amiss somewhere (perhaps in the Msys dll, or the Pascal runtime
>library). Perhaps I should just stick to testing under Cygwin and Mingw
>- but it would be a shame to abandon Msys if the problem can easily be
>solved.
>
>
I am willing to help you debug MSYS.
1) cp -a /c/msys/1.0 /c/msys/debug
2) cd msys/build/directory && make clean
3) ccflags='-O0 -g -fnative-struct -DDEBUGGING'
OR
3) ccflags='-O0 -g -fnative-struct -DTRACING'
OR
3) ccflags='-O0 -g -fnative-struct -DDEBUGGING -DTRACING'
4) make CFLAGS="$ccflags" CXXFLAGS="$ccflags"
5) cp i686-pc-msys/winsup/cygwin/new-msys-1.0.dll
/c/msys/debug/bin/msys-1.0.dll
Startup the debug version of MSYS and use strace or DbgView to debug
it. Caution, all process are slower; use the debug version only for
debugging. Caution, comparison to the Cygwin code as it exists today is
fruitless. Hint: Copy the desktop icon and modify the properties of the
copy to point to the /c/msys/debug/msys.bat and /c/msys/debug/bin
directories.
I'll be looking forward to a patch.
HTH,
Earnie
--
http://www.mingw.orghttp://sourceforge.net/projects/mingwhttps://sourceforge.net/donate/index.php?user_id=15438

On 21 May 2004 at 16:30, Earnie Boyd wrote:
> Is example1.exe a msys-1.0.dll dependent binary?
Yes.
> I've stated before that I'm not really interested in supporting someone
> else's use of the msys runtime;
Fair enough - I thought I'd ask anyway, since the same programs,
compiled for Mingw and Cygwin, work perfectly fine and don't exhibit
this problem.
> however, you should check your use of the memory heap. You've
> exceeded the amount of space allocated for your use.
That is what the Msys system has decided - but the test program does
not (at least, it is not supposed to) use much memory at all. Indeed,
all it does is to use the functionality of a (Pascal) class library
that I am building to create a top-level window that does nothing. I am
not sure however how to check my use of the memory heap or how such a
trivial program could exceed the allocated heap space (where is the
heap space allocated, and how much is allocated?).
I am trying to support all Win32 gnu platforms with this class library.
I have checked the header flags in the executable for reserved and
allocated stack and heap space. These are exactly the same in the
Cygwin, Mingw, and Msys executable (as they should be), since the code
is exactly the same, and uses the same Winapi calls. So something is
amiss somewhere (perhaps in the Msys dll, or the Pascal runtime
library). Perhaps I should just stick to testing under Cygwin and Mingw
- but it would be a shame to abandon Msys if the problem can easily be
solved.
Best regards, The Chief
--------
Prof. Abimbola A. Olowofoyeku (The African Chief)
web: http://www.greatchief.plus.com/