Jump to content

  • Log In with Google      Sign In   
  • Create Account

Banner advertising on our site currently available from just $5!


1. Learn about the promo. 2. Sign up for GDNet+. 3. Set up your advert!


entry point __CxxFrameHandler3 could not be located


Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

  • You cannot reply to this topic
4 replies to this topic

#1 DiPharoH   Members   -  Reputation: 100

Like
0Likes
Like

Posted 12 May 2008 - 10:46 PM

i am using:- Directx feb 2007 Directx10 winxp i developed ann app when i run it crashes whith this error "the procedure entry point __CxxFrameHandler3 could not be located in thr dynamic link library msvcrt.dll" so is there any way notto link with msvcrt.dll and link with msvcrtd.dll or msvcrtd0.dll??? i think the problem that framehandler3 is for vista can anyone help??????

Sponsor:

#2 Evil Steve   Members   -  Reputation: 1986

Like
0Likes
Like

Posted 12 May 2008 - 11:36 PM

What compiler are you using? It's not VC6 is it?

#3 DiPharoH   Members   -  Reputation: 100

Like
0Likes
Like

Posted 13 May 2008 - 12:33 AM

i am using visual c++ 2008

#4 jollyjeffers   Crossbones+   -  Reputation: 1542

Like
0Likes
Like

Posted 13 May 2008 - 01:09 AM

There are various mentions of this linker error online. From having done your preliminary research for you it would suggest that this is a general problem with mis-matched libraries and is a general C/C++ problem rather than a DirectX specific one.

I suggest you check your compiler/IDE configuration as well as SDK installations. Moved to 'General Programming' for further discussion.

You may also find this bit of reading interesting, albeit not a solution:
Quote:
From CodeProject:
I've realized what the mysterious __CxxFrameHandler3 is for. When the compiler generates exception records for objects destructors it places there a reference to this function, which gets as parameters the frame info (including the list of destructors to be called) and is responsible for the following things:

1. Examine the exception and decide whether this block catches it.
2. Call the destructors during the unwind.


hth
Jack
<hr align="left" width="25%" />
Jack Hoxley <small>[</small><small> Forum FAQ | Revised FAQ | MVP Profile | Developer Journal ]</small>

#5 DiPharoH   Members   -  Reputation: 100

Like
0Likes
Like

Posted 13 May 2008 - 01:36 AM

thanks mate
but it's not a linking error
it compiles well
but when i run the app
that's what happen




Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.



PARTNERS