About memory leaks
-
Is the debugger in VC++ always indicating mem leaks, or is it necessary to change the settings ? ~RaGE();
VC++ debugger does not indicate the memory leaks. You can use CRT libary programatically to check the memory leaks, but this is of not great help compred to third party tools like BoundsChecker, etc. Thanks, Ramy
-
VC++ debugger does not indicate the memory leaks. You can use CRT libary programatically to check the memory leaks, but this is of not great help compred to third party tools like BoundsChecker, etc. Thanks, Ramy
Ramu Pulipati wrote: VC++ debugger does not indicate the memory leaks. Hem .. actually it does :| ... what I want is (surprisingly) not to know _where_ are memory leaks, but to know if _there are_ memory leaks ... To be a little bit more clear, I have developped an API. In a test program for this API, I do not have any mem leaks detected by the debugger. But when I use some functions from this API into a more consequent mem leaks free application, then I get the memory leaks. So i suppose this __must_ be the API, and hence I´ve concluded that in the big application, project settings must have changed so that it indicates mem leaks :~ . Is that clear or are you already :zzz: :zzz: (BTW is that a new emoticon ? Never saw it before ??)? ~RaGE();
-
Ramu Pulipati wrote: VC++ debugger does not indicate the memory leaks. Hem .. actually it does :| ... what I want is (surprisingly) not to know _where_ are memory leaks, but to know if _there are_ memory leaks ... To be a little bit more clear, I have developped an API. In a test program for this API, I do not have any mem leaks detected by the debugger. But when I use some functions from this API into a more consequent mem leaks free application, then I get the memory leaks. So i suppose this __must_ be the API, and hence I´ve concluded that in the big application, project settings must have changed so that it indicates mem leaks :~ . Is that clear or are you already :zzz: :zzz: (BTW is that a new emoticon ? Never saw it before ??)? ~RaGE();
Yes, it's a new emoticon. VC *tries* to detect memory leaks, third party products do it better. Christian I am completely intolerant of stupidity. Stupidity is, of course, anything that doesn't conform to my way of thinking. - Jamie Hale - 29/05/2002 Half the reason people switch away from VB is to find out what actually goes on.. and then like me they find out that they weren't quite as good as they thought - they've been nannied. - Alex, 13 June 2002
-
Yes, it's a new emoticon. VC *tries* to detect memory leaks, third party products do it better. Christian I am completely intolerant of stupidity. Stupidity is, of course, anything that doesn't conform to my way of thinking. - Jamie Hale - 29/05/2002 Half the reason people switch away from VB is to find out what actually goes on.. and then like me they find out that they weren't quite as good as they thought - they've been nannied. - Alex, 13 June 2002
VC detects mem leaks by use of redirecting new and delete functions. When u'r using API calls for allocation and such, VC debugger can't see that. For these leaks use boundschecker and such.. :rolleyes:
-
VC detects mem leaks by use of redirecting new and delete functions. When u'r using API calls for allocation and such, VC debugger can't see that. For these leaks use boundschecker and such.. :rolleyes:
-
Is the debugger in VC++ always indicating mem leaks, or is it necessary to change the settings ? ~RaGE();
I suspected that I had a memory leak or handle leak of some sort and have spent ages trying to find it. The other day I found a free 30 day demo for an app called GlowCode. It was really easy to use, you don't change your code, just attach it to your app while its running. Anyway I found my problem in a couple of hours :-D . I thought you might be interested, here's the link .... http://www.glowcode.com/ Ali
-
I suspected that I had a memory leak or handle leak of some sort and have spent ages trying to find it. The other day I found a free 30 day demo for an app called GlowCode. It was really easy to use, you don't change your code, just attach it to your app while its running. Anyway I found my problem in a couple of hours :-D . I thought you might be interested, here's the link .... http://www.glowcode.com/ Ali