Berocoder 24 Posted Monday at 01:08 PM (edited) From SO https://stackoverflow.com/questions/79332724/assert-raise-no-exception It feels like I tried everything. Asserts logs fine with a new application but not in the real big application. Any hints what to do ? Edited Monday at 01:09 PM by Berocoder Edit link Share this post Link to post
Kas Ob. 124 Posted Monday at 01:36 PM Can you confirm the assertion code is there ? (i mean the compiler did add the code ) I ran of something similar but it was the IDE fault, sometimes disabling the assertion in project options, and then re-enabling them is not enough for some reason the compiler will not add them until calling clean on the project or closing the project and re-open it, this happen on XE8. In all cases put a break point and see if the assert code in assembly is there, also it could be a forgotten directive somewhere. Share this post Link to post
Berocoder 24 Posted Monday at 01:40 PM (edited) 1 minute ago, Kas Ob. said: Can you confirm the assertion code is there ? (i mean the compiler did add the code ) I ran of something similar but it was the IDE fault, sometimes disabling the assertion in project options, and then re-enabling them is not enough for some reason the compiler will not add them until calling clean on the project or closing the project and re-open it, this happen on XE8. In all cases put a break point and see if the assert code in assembly is there, also it could be a forgotten directive somewhere. The actual Assert is triggered and catched by Delphi IDE. It is just that it is not catched by EurekaLog. So there is no EL-logfile and my event OnExceptionNotify is not called Edited Monday at 01:41 PM by Berocoder Share this post Link to post
Anders Melander 1819 Posted Monday at 01:46 PM EL might be conditionally redirecting the Assert handler. Place a breakpoint in System._Assert to verify that the Assert code is being called. Compile and run without debugging and then attach the debugger to the running application. Share this post Link to post
Attila Kovacs 632 Posted Monday at 02:13 PM Did EL linked itself to the exe without any errors? Share this post Link to post
Berocoder 24 Posted yesterday at 10:01 AM Problem solved. It was my mistake. ApplicationEvents.OnException := nil; I believed that this disabled old JCL that was used before. But it seems to disable whole exception mechanism for software exceptions. Hardware exceptions still works. Share this post Link to post