I removed the (demo) EurekaLog integration from my app, but doing that caused me to lose my stack trace capability (even though I had specifically added the JCL Debug unit to my project to be able to keep that. So, I found out what I was doing wrong and fixed it. No problemo - until I protected the app with Enigma.
If I run the app after processing it with Enigma, EVEN WITH EVERYTHING DISABLED, the JclStartExceptionTracking function returns False. If I bypass Enigma and run the app, JclStartExceptionTracking returns True and stack tracing works great.
I'm generating and keeping a MAP file (even though I'm having JCL Debug generate the .jdbg file and embed it in the app). As far as settings are concerned, see the attached images.
So, I'm at an impasse again. I have no clue how to fix this on my own. Help!
Can't use JCL Debug for stack trace with Enigma
-
oHXD3OUsHe
- Posts: 12
- Joined: Mon Oct 11, 2021 3:30 pm
-
oHXD3OUsHe
- Posts: 12
- Joined: Mon Oct 11, 2021 3:30 pm
Re: Can't use JCL Debug for stack trace with Enigma
Sorry, no attached images (I copied this from an email). My bad!
-
oHXD3OUsHe
- Posts: 12
- Joined: Mon Oct 11, 2021 3:30 pm
Re: Can't use JCL Debug for stack trace with Enigma
I ditched the JCL Debug stuff, and bought and integrated EurekaLog. If you follow their recommendations, you can get a stack trace while still using Enigma. Just use E.StackTrace (where E is the Exception instance)...