Re: [semi-OT] gdb backtrace on windows

[Dan Kegel <dank kegel com>]

On Mon, Oct 19, 2009 at 12:52 PM, Tor Lillqvist <tml iki fi> wrote:
> The most likely cause for weird errors is heap corruption. Does your
> program run on Linux? Have you tried running it under valgrind to find
> heap corruption errors? (See http://live.gnome.org/Valgrind for
> instructions, in particular the use of G_SLICE=always-malloc is
> important.)

Yeah, if you can repeat it on Linux, you may have an easier
time of debugging it.

For what it's worth, I've gotten Valgrind to work and give good stack traces
with Wine (for apps compiled with visual C).  It might be worth trying
in a pinch if you can't reproduce on Linux.