Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

Memory leak when return char* from DLL

22 Posts 7 Posters 0 Views 1 Watching

N Niklas L

shivanandgupta wrote:

if we use cData='\0' and after this "delete []cData;" then memory leak still continue.

Well, if you set cData to '\0' you are manipulating the pointer, not the data it contains. cData is set to null, and that is what you try to delete (and it always succeeds.) Doesn't the DLL supply an API for freeing this string? IMHO dll's should always be designed that way.

home
S Offline
S Offline
Shivanand Gupta

wrote on last edited by

#21

if we use delete without using '\0' then problem occur about heap at run time.
N 1 Reply Last reply

0
S Shivanand Gupta

if we use delete without using '\0' then problem occur about heap at run time.
N Offline
N Offline
Niklas L

wrote on last edited by

#22

Well, setting it to '\0' is the same as setting it to NULL. In either case, it makes the delete call a no-op, and that's why you don't get a crash, but you DO get a memory leak.

home
1 Reply Last reply

0

Log in to reply

1
2