Heap Alloc Exception Problem

[Adam Hartshorne]

Hi All,

I have the strangest problem, and at an end to try and explain it/know
what to do.

I have a program written in c++ using visual studio 7.1. It was all
working no problems, then after not changing the code or recompiling
between two runs using the debugger I all of a sudden got the following
error.

unhandled exception at 0x0012fe01 in multiselect.exe: 0x0c0000005

and this occurred in malloc.c at line 212 which is at the end of the
heap alloc method.

Well I thought maybe I did change my code between runs, but I am pretty
sure I didn't. Luckily I had a recent backup, again fully working, and I
wiped my code, and replaced it with the backup.

I rebuilt the whole project, and tried running the backup. To my shock
and horror the same error message appeared and crashed my program.

I have no clue what is causing this, and no idea how to proceed now. Any
suggestions would be much appreciated,

Adam

 

[Peter Koch Larsen]

Hi All,

I have the strangest problem, and at an end to try and explain it/know
what to do.

I have a program written in c++ using visual studio 7.1. It was all
working no problems, then after not changing the code or recompiling
between two runs using the debugger I all of a sudden got the following
error.

unhandled exception at 0x0012fe01 in multiselect.exe: 0x0c0000005

and this occurred in malloc.c at line 212 which is at the end of the heap
alloc method.

Well I thought maybe I did change my code between runs, but I am pretty
sure I didn't. Luckily I had a recent backup, again fully working, and I
wiped my code, and replaced it with the backup.

I rebuilt the whole project, and tried running the backup. To my shock and
horror the same error message appeared and crashed my program.

I have no clue what is causing this, and no idea how to proceed now. Any
suggestions would be much appreciated,

Adam

You have corrupted your head somehow, e.g. by overwriting memory somewhere
or by freeing twice. This causes undefined behaviour. One possibility is
raising an exception, another is continuing as if everything worked
perfectly.

/Peter

 

[Adam Hartshorne]

You have corrupted your head somehow, e.g. by overwriting memory somewhere
or by freeing twice. This causes undefined behaviour. One possibility is
raising an exception, another is continuing as if everything worked
perfectly.

/Peter

I am not sure I fully understand what you are saying. My problem has got
even stranger, I have commented out all my code, and I still get the
problem when I run it up.

I should say at this point I am using two other libraries, and so
although I have commented all my code, there is still a few lines calls
other people methods. One for instance is the call to qglViewer to
create a new viewer. Could it be that those dll or something have become
corrupted?

Adam

 

[Adam Hartshorne]

I am not sure I fully understand what you are saying. My problem has got
even stranger, I have commented out all my code, and I still get the
problem when I run it up.

I should say at this point I am using two other libraries, and so
although I have commented all my code, there is still a few lines calls
other people methods. One for instance is the call to qglViewer to
create a new viewer. Could it be that those dll or something have become
corrupted?

Adam

Problem solved, it appears that the dll for the QGLViewer decided to
corrupt itself :-(. I have now rebuilt it, and life is back to normal.

Sometimes I hate computers for doing things like that. Justed wasted a
whole day because windows corrupted my dll!

Adam

 

[Larry I Smith]

Problem solved, it appears that the dll for the QGLViewer decided to
corrupt itself :-(. I have now rebuilt it, and life is back to normal.

Sometimes I hate computers for doing things like that. Justed wasted a
whole day because windows corrupted my dll!

Adam

I wouldn't know. I don't use Windows.

Larry

 

[Artie Gold]

You have corrupted your head somehow, e.g. by overwriting memory somewhere

^^^^

That may be the case -- but ITYM `heap'! ;-)

or by freeing twice. This causes undefined behaviour. One possibility is
raising an exception, another is continuing as if everything worked
perfectly.

/Peter

--ag

 

[Peter Koch Larsen]

Peter Koch Larsen wrote: [snip]

You have corrupted your head somehow, e.g. by overwriting memory
somewhere

^^^^

That may be the case -- but ITYM `heap'! ;-)

Sure!
Sometimes these problems could be the result of a "head-problem", however
;-)

/Peter
[snip]