#546 debugging causes fatal exception 0E

[Anonymous]

Hello developers,
I'd like to report a really strange behavior when I try to debug...

I can see than starting with DevC++ 4.9.8.10 until now (4.9.9.2) I'm
not able to debug at all.

I've tried run on Windows 98 SE, Windows ME (both Czech
localizations), Gigabyte MB, nVidia5200 Sparkle (AGP 8x) with
installed nVidia drivers. Dev-C++ and MinGW inside.

I also tried Pentium II boxed on Windows 98 SE (Czech loc.),
PCChips 715 MB and ATI Rage 128 (AGP 1x), Dev-C++ and
MinGW inside with the same observations- debugging regulaarly
crashes.

There is no problem on Windows 95 OSR2+QEMM, PC Chips M517,
ATI Rage Pro (PCI) and K6-2. On this machine and Windows Dev
C++ debugs fine....

Now to the observations:
~~~~~~~~~~~~~~~~~~~~
When I push the 'tick' debug button Windows 98 SE/ME Dev C++
propts the message about including the debug info. The
recompilation with debug info is done fine. But just after that (I except
that gdb is invoked) Windows stops with the blue screen of death:

Fatal Exception 0E.

I confirm by Enter and then Windows kills Dev C++. So I'm not able
to report the stack and registers because of the fact that windows
kills Dev c++.

I could eventually understood instability in case of complex cources,
but I've tried very small programs like 'Hello world', just printf....

As far as I can say it is the platform (os) dependent.
I wasn't able to debug with Dev-C++ on Win98 and later.

Thanks for your effort. ... dev-c++ is going to be the brilliant
developing tool! ...

Please contact me in case of need of more info...

Kind Regards,
F_II, F_II@email.cz

[Marek Januszewski]

Logged In: YES
user_id=609236

I'm not sure if we're going to support win95 as nobody from
the team has a system that old. can you reproduce it with
windows 2000 and up?

[Nobody/Anonymous]

Logged In: NO

I have the same error as You.
I've found that the compiler settings (inclusion of debug
information) aren't changed during next compilation, and the
sources are compiling with old settings (i.e. no debug
info). Attempt to debug file compiled in such way causes the
error.
Shutting down DevC++, and reloading project again sometimes
helps, but not always.

The problem is not only with debugging. None of compiler
options can be altered while DevC++ is running.They will be
simply not applied during compilation.

You can hower check whether new settings was applied by
examining size of output file. For example - without debug
info my .exe file is less than about 8kB, with debug info
it's more than 300kB.