Thursday, September 07, 2006

Again!!!!



This time have to find out how!!!!

15 Comments:

Blogger Unknown said...

It's a bug in the game maga! Its somehow ending up calling a pure virtual function which does not have a definition! So, it goes kaput!

Friday, September 08, 2006  
Blogger Unknown said...

The same thing happened in Yahoo! messenger, remember???

yahoobug

Friday, September 08, 2006  
Blogger Unknown said...

Its not a VC++ problem, its the problem of the software that throws up the error...

Friday, September 08, 2006  
Blogger Unknown said...

Did you press the "debug" button?? Don't tell me that you did not!!

Friday, September 08, 2006  
Blogger Unknown said...

@Srini - its true its the s/w or should I say the compiler let the buggy function call sneek thru..

say the variable to abstract base class which has this pvf was not a pointer, but a normal variable.. the call wont go to the derived class with the function implemented alva? the compiler was dumb to let this in???

and btw if I had pressed debug button, I would have got the stack trace/dump with all memory addresses... adan itkond en madli!! EA sportsge kalsla ;) this happened during playing pirated version of ur game antha :D

Friday, September 08, 2006  
Blogger Unknown said...

It HAS to be a pointer which caused this. Otherwise virtual functions don't make sense right?

Friday, September 08, 2006  
Blogger Unknown said...

@Srini - Now, I agree it has to be a pointer, how did the code ever compile in the first place if the function call would never come down to where it was implemented?!??! Are all the compilers unaware of this?!?

someplace in web...

A pure function should never be invoked. However, a buggy program or a buggy compiler can sometimes call a pure virtual function. In general, when a pure virtual function is invoked, the program crashes and you cannot continue debugging it.

Friday, September 08, 2006  
Blogger Unknown said...

What MICROSOFT has to say fot it...

This error occurs when your application indirectly calls a pure virtual member function in a context where a call to the function is not valid. In most cases, the compiler detects this and reports the error when building the application. But depending on how your code is written, sometimes the problem is detected only at run-time.

The error occurs when you indirectly call a pure virtual function within the context of a call to the constructor or destructor of an abstract base class. This is illustrated in the sample code below, along with some more description.
MS

Friday, September 08, 2006  
Blogger Unknown said...

Yep - depends on how its coded... Compilers are not all powerful in some cases to detect every possible flaw...

Friday, September 08, 2006  
Blogger Unknown said...

@Srini - hmm.. bad programmers in Yahoo! and EA Sports huh! :D

Friday, September 08, 2006  
Blogger Vinay V said...

If people like you, who can afford the game, who are passionate about the game, are not willing to pay for it, how do you expect EA Sports to pay it's employees well & employ only the best programmers?

STOP playing pirated games.. Stop piracy.

Monday, September 11, 2006  
Blogger Unknown said...

@VV - Point taken boss!

Monday, September 11, 2006  
Blogger Unknown said...

@VV - If u want to be reminded.. look whos talking abt pirated merchandise!!!! remember the talk abt Ferrari Merchandise?!??!

Monday, September 11, 2006  
Blogger Aditya Kulkarni said...

@VV WTF? Stop piracy? Are you mad?

Tuesday, October 24, 2006  
Anonymous Anonymous said...

good job...

Wednesday, February 20, 2008  

Post a Comment

Subscribe to Post Comments [Atom]

<< Home