I got the same problem and I spent lots of time trying to figure out how
to use mpatrol in MINGW. I came accross a post here that it could have
been caused by incompatible compiler versions that was used in creating
mpatrol binaries for Windows so I tried compiling the source myself. The
compile sequence was a breeze. Just make sure that you run "make" under
<mpatrol_directory_source>\build\mingw32. As of now, I can run my
binaries link against mpatrol just fine.

Here my system information:
OS : Windows XP SP2
G++ verion : 3.4.4

HTH,
Quantufinity

Note that I didn't use -lwatt32 because I don't know what's the purpose
of that library.


--- In mpatrol@yahoogroups.com, Gisle Vanem <giva@...> wrote:
>
> No matter what and how I link my test app, mpatrol calls abort():
> This application has requested the Runtime to terminate it in an
unusual way.
> Please contact the application's support team for more information.
>
> I've built my static lib (libwatt32.a) with <mpatrol.h> included last
in all it's
> sources. I link the test app. with
> gcc ... -lwatt32 -lmpatrolmt -lbfd -liberty -limagehlp
>
> I have done 'set MPATROL_OPTIONS=LOGALL'. After running my app,
> mpatrol.log contains this traceback:
>
> ERROR: [ILLMEM]: illegal memory read at address 0x00000000
> 0x00000000 not in heap
>
> call stack
> 0x00000000 ???
> 0x0044BEAC ???
> 0x0043D80C ???
> 0x0043E273 ???
> 0x0043CC2F ???
> 0x0049B98C ???
> 0x0049B817 ???
> 0x00401541 ???
> 0x004011E7 ???
> 0x00401238 ???
> 0x7C816D4F RegisterWaitForInputIdle+73
>
> Building w/o mpatrol, the program works fine. So the "read at address
0"
> is not true (I would have gotten a GPF from Windows).
>
> I would be happy if mpatrol could provide symbol names. Isn't that
possible
> with MingW 3.3 and 'gcc -g'?
>
> --gv
>