There can be as many causes for a GPF as there are lines of code in a program. Some common causes include. Generic Remove all generated files and do a full recompile: CLW, INC, OBJ, RSC, EXP, LIB, MAP, EXE, DLL. Compile with full debug information. Enable project options runtime checks: Index out…

see also [image] Use of ASSERT statements in procedures with a CriticalProcedure can lead to... code I had occasion to run across an old bug (reported in 2013) in the ABC library which hasn’t been fixed yet, but which can be fi…

ClarionHub

Hunting down nasty GPF's

questions tips

gpf

elankreijer February 26, 2020, 1:11pm 3

See also

How to improve the Call Stack when your program GPFs to show Procedure Names in Stack Trace Tips

As shown on ClarionLive (2014, Sept 19) When you GPF you’re given a stack trace with several fairly useless addresses However if you’re in Debug mode and have %Bin%\Debug\ClaRun.dll in place then in addition to the (fairly useless) addresses, you also get the ModuleName:LineNumber -Procedure (note: routines appear with a R$ prepended to their name) So using the %Bin%\Debug\ClaRun.dll is a great thing. However, every time you compile, the IDE copies over the ClaRun.dll with the %Bin%\C…

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled