# Assertion failure on memory deallocation C++ CLR [solved]

This topic is 3623 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

## Recommended Posts

##### Share on other sites
Quote:
 Original post by GuthurAlready done assemblier, a bit anyway, 6502 back at school and the IBM assemblier. Its ok but to be honest I want to have tangible results, in terms of functional applications, and to be playing with assemblier would just be a major distraction. Also i'd like to concentrate on C++ for awhile, there is alot to learn about. And then when you throw in C# and .NET :s

My point was not in learning assembly to code in but to use the debugger meaningfully. Because looking at the disassembly and stepping through it (and keeping tabs on what happens in memory) you'd be able to *easily* see for yourself where things go wrong.

The point to learning assembly is to not be as dependent on outside help for finding and fixing bugs. (As well as understanding C++ better. Without learning basics (only basics!) of assembly quite a few things about C++ might not get properly understood.)

But you're right: understanding most of C++ properly has to have priority, I guess. :-)
But don't think learning the basics of assembly has no relevance to understanding C++ properly. You'd be dead wrong. But most importantly it's important is for *debugging*.

Alex

##### Share on other sites
Point taken Alex, its a fair point and one I will definitely take on board. I wish i had the time to delve into assemblier is all i meant :) If the problem is that deep then i'm just going to let it leak and mark it down to be looked at later.

I have spent long enough gluing these projects together, I want to get back to making the application :). I now know a lot more about making dll's and creating wrappers for managed code to use unmanaged libs, it should be worthwhile knowledge i think.

##### Share on other sites
Quote:
 Original post by GuthurPoint taken Alex, its a fair point and one I will definitely take on board. I wish i had the time to delve into assemblier is all i meant :) If the problem is that deep then i'm just going to let it leak and mark it down to be looked at later. I have spent long enough gluing these projects together, I want to get back to making the application :). I now know a lot more about making dll's and creating wrappers for managed code to use unmanaged libs, it should be worthwhile knowledge i think.

Sure. But if you want to drastically improve your C++-Skills beyond what can be picked through coding itself, read first Effective C++ and then pick up some assembly basics until you understand exactly what your application is doing in disassembly.

Alex

1. 1
Rutin
32
2. 2
3. 3
4. 4
5. 5

• 13
• 77
• 11
• 10
• 14
• ### Forum Statistics

• Total Topics
632968
• Total Posts
3009583
• ### Who's Online (See full list)

There are no registered users currently online

×