E
Easter Bunny
Dear group,
If/when my program crashes on a unix type OS, there is a core dump
written to disk that allows me to debug the problem *after* the
failing process has already terminated; I can even take the core
dump from the customer and analyze the problem on my developer
machine later.
One of our portable C programs crashes only when compiled for the
MS Windows operating system. We are using lcc-win32 for that.
In this environment, neither is there a core dump generated, nor
does the lcc-win32 debugger provide any facilities to read such a
thing.
How does one debug programs compiled with lcc-win32 post mortem?
Is there a general way, or is my problem platform specific?
Please help, I'm being under a lot of stress this time of the year.
Many thanks!
If/when my program crashes on a unix type OS, there is a core dump
written to disk that allows me to debug the problem *after* the
failing process has already terminated; I can even take the core
dump from the customer and analyze the problem on my developer
machine later.
One of our portable C programs crashes only when compiled for the
MS Windows operating system. We are using lcc-win32 for that.
In this environment, neither is there a core dump generated, nor
does the lcc-win32 debugger provide any facilities to read such a
thing.
How does one debug programs compiled with lcc-win32 post mortem?
Is there a general way, or is my problem platform specific?
Please help, I'm being under a lot of stress this time of the year.
Many thanks!