Jump to content

  • Log In with Google      Sign In   
  • Create Account


- - - - -

Error in std::bad_alloc (debug)


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
2 replies to this topic

#1 VitaliBR   Members   -  Reputation: 147

Like
0Likes
Like

Posted 30 July 2012 - 07:11 AM

I'm trying to understand, since I asked google for help and nothing ...
In my lib have a method of a class as follows:

bool SDX_Model::Load(const std::string& pFile)

When I run my test project (for testing lib) in Debug mode in VS2010 him of this error:

Unhandled exception at 0x770615de in teste_dx.exe: Microsoft C++ exception: std::bad_alloc at memory location 0x0034efc4..


headers in my file:
#include <iostream>
#include <iostream>
#include <fstream>
#include <assimp/Importer.hpp>	  // C++ importer interface
#include <assimp/scene.h>		   // Output data structure
#include <assimp/postprocess.h>	 // Post processing flags
#include "../../include/SDX_Model.h"
#pragma comment (lib, "assimp.lib")

with the file (mlock.c) open and the piece of code in focus:

/***
* _unlock - Release multi-thread lock
*
*Purpose:
*	   Note that it is legal for a thread to aquire _EXIT_LOCK1
*	   multiple times.
*
*Entry:
*	   locknum = number of the lock to release
*
*Exit:
*
*Exceptions:
*
*******************************************************************************/
void __cdecl _unlock (
	    int locknum
	    )
{
	    /*
		 * leave the critical section.
		 */
	    LeaveCriticalSection( _locktable[locknum].lock );
}

The strange thing is that when road in Release mode, everything works OK

Sponsor:

#2 kuramayoko10   Members   -  Reputation: 386

Like
0Likes
Like

Posted 20 August 2012 - 09:51 AM

Could you post more of your code on the .cpp file? The exact line it breaks?

Also it would be very helpful with you showed the dissasembly for this file.
Right-click on your code and select the option "Show dissasembly" or something like that on VS2010.
Programming is an art. Game programming is a masterpiece!

#3 BitMaster   Crossbones+   -  Reputation: 3883

Like
1Likes
Like

Posted 30 August 2012 - 05:48 AM

That piece of code (mlock.c) is very unlikely to be the actual problem, it is one of those places where things often fall apart when you have screwed something up before. Walk up the call stack until you reach the first code either written by yourself or Assimp. Whatever is happening there will probably give hints abouts the actual problem.




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