 |
forums.silverfrost.com
Welcome to the Silverfrost forums
|
| View previous topic :: View next topic |
| Author |
Message |
KennyT
Joined: 02 Aug 2005
Posts: 318
|
 Posted: Fri Mar 19, 2010 5:18 pm Post subject: Trapping runtime errors, with windows C++ and FTN95 DLLs |
 |
|
Got a nasty one!
We're calling a C++ DLL which is providing a windows interface capability. It's called "Qt" (if anyone happens to be familiar with it!).
The problem is that for some unknown reason, the app has started crashing. The traceback provided by FTN indicates that the crash is in the C++ DLL, but, according to our tame C++ programmer, he doesn't get a trap in his debugger (visual studio, I assume) before FTN has fallen over.
So, is there a way to stop FTN intercepting the crash, so that the VS debugger has a chance to see what's going on?
K |
|
| Back to top |
|
 |
acw
Joined: 04 Nov 2005
Posts: 165
Location: Darkest Devon
|
| Posted: Mon Apr 19, 2010 12:33 pm Post subject: |
|
|
| I don't know if this is what you're doing already, but to debug C++ code in a dll called from ftn95 (using visual studio), I start the app in non-debug mode (ctrl+f5 or just run the exe from explorer), then once started I use the VS debug->attach to process to select the running executable using the VS native debugger (rather that the ftn95 debugger). Breakpoints or crashes in the c++ code should then happen as expected in VS. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
