Re: Please help me, i got message Assertation falure line 47 _block_type_is_valid(phead->nBlockType) with following code

usman911@xxxxxxxxx wrote:

//goal: to make a 2 dimentional dynamic array and use it in matrix
multiplication plz help me, //i am using VC++
#include<iostream.h>

[snip]

Don't use <iostream.h>, use <iostream>.

When you get an assertion failure, attach the debugger (if you are not running under it) and follow the call stack to the place in YOUR code that caused this assertion. The error is not in dbgdl.cpp!

David Wilkinson
.

Relevant Pages

  • Re: attach to windows form app (release mode)
    ... I can't see the stack or local variables - symbols are not ... Here you can see the effects of JIT optimizations. ... under debugger, it by default disables JIT optimizations, and as a result you can ... and when you attach after that, ...
    (microsoft.public.vsnet.debugging)
  • Re: Often lock ups in vs2k5
    ... I start the application in the debugger. ... break it in the morning and I get that call stack. ... I have also tried to run in out of the bugger then attach with managed ... It means that the debugger is working in native mode, ...
    (microsoft.public.vsnet.debugging)
  • Re: EnumChildWindows
    ... The important thing when you get an assertion failure is to drop into the debugger and ... best-guess rather than being absolutely confident that it is the problem. ...
    (microsoft.public.vc.mfc)
  • Re: "assert" annoyance
    ... > What I really want is for any assertion failure, ... to trap to the debugger WITHOUT blowing out of the scope ...
    (comp.lang.python)