U++ framework: Newbie corner » CTRL + C = 659 Heap leaks

Home » Community » Newbie corner » CTRL + C = 659 Heap leaks

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

Re: CTRL + C = 659 Heap leaks [message #52047 is a reply to message #52039]

Thu, 11 July 2019 17:10

Novo
Messages: 1431
Registered: December 2006

Ultimate Contributor

Xemuth wrote on Thu, 11 July 2019 03:36

Quote:
AFAIK, you can click on memory leaks in TheIDE, and it will show you where this memory was allocated. I can be wrong, I haven't seen memory leaks in my code for very very long time Rolling Eyes

How you do it ? I get all the memory leak by looking log on theIDE but it's not clickable

I, probably, saw that somewhere else ...

Another approach:
1) compile your code with a .USEMALLOC flag. That will switch to glibc's allocator
2) run valgrind your_app
3) press CTRL-C

you will get detailed information about memory leaks.

There is also Debug --> "Test in Valgring" in TheIde, but I personally always use valgrind from command line ...

Regards,
Novo

Report message to a moderator

[Message index]

		CTRL + C = 659 Heap leaks By: Xemuth on Wed, 10 July 2019 21:05
		Re: CTRL + C = 659 Heap leaks By: Novo on Thu, 11 July 2019 06:06
		Re: CTRL + C = 659 Heap leaks By: Xemuth on Thu, 11 July 2019 09:36
		Re: CTRL + C = 659 Heap leaks By: Oblivion on Thu, 11 July 2019 09:57
		Re: CTRL + C = 659 Heap leaks By: Novo on Thu, 11 July 2019 17:10
		Re: CTRL + C = 659 Heap leaks By: Xemuth on Thu, 11 July 2019 10:10
		Re: CTRL + C = 659 Heap leaks By: mirek on Thu, 11 July 2019 10:22
		Re: CTRL + C = 659 Heap leaks By: Novo on Thu, 11 July 2019 16:42
		Re: CTRL + C = 659 Heap leaks By: mirek on Fri, 12 July 2019 00:15
		Re: CTRL + C = 659 Heap leaks By: mirek on Fri, 12 July 2019 00:18
		Re: CTRL + C = 659 Heap leaks By: Novo on Fri, 12 July 2019 00:46
		Re: CTRL + C = 659 Heap leaks By: mirek on Fri, 12 July 2019 09:44
		Re: CTRL + C = 659 Heap leaks By: mirek on Fri, 12 July 2019 09:55
		Re: CTRL + C = 659 Heap leaks By: Novo on Mon, 15 July 2019 06:15
		Re: CTRL + C = 659 Heap leaks By: mirek on Mon, 15 July 2019 08:17
		Re: CTRL + C = 659 Heap leaks By: Novo on Mon, 15 July 2019 17:16
		Re: CTRL + C = 659 Heap leaks By: mirek on Mon, 15 July 2019 19:35
		Re: CTRL + C = 659 Heap leaks By: Novo on Mon, 15 July 2019 20:18
		Re: CTRL + C = 659 Heap leaks By: mirek on Tue, 16 July 2019 00:11
		Re: CTRL + C = 659 Heap leaks By: Novo on Tue, 16 July 2019 02:11
		Re: CTRL + C = 659 Heap leaks By: mirek on Tue, 16 July 2019 09:38
		Re: CTRL + C = 659 Heap leaks By: Novo on Wed, 17 July 2019 18:44
		Re: CTRL + C = 659 Heap leaks By: mirek on Wed, 17 July 2019 20:25
		Re: CTRL + C = 659 Heap leaks By: mirek on Wed, 17 July 2019 23:04
		Re: CTRL + C = 659 Heap leaks By: Novo on Wed, 17 July 2019 23:46
		Re: CTRL + C = 659 Heap leaks By: mirek on Tue, 23 July 2019 09:36
		Re: CTRL + C = 659 Heap leaks By: Xemuth on Thu, 11 July 2019 10:28
		Re: CTRL + C = 659 Heap leaks By: Xemuth on Thu, 11 July 2019 10:30
		Re: CTRL + C = 659 Heap leaks By: Xemuth on Thu, 11 July 2019 22:13
		Re: CTRL + C = 659 Heap leaks By: Novo on Thu, 11 July 2019 22:24
		Re: CTRL + C = 659 Heap leaks By: Novo on Thu, 11 July 2019 22:31
		Re: CTRL + C = 659 Heap leaks By: Xemuth on Fri, 12 July 2019 09:28

Previous Topic:	How i can play a sound?? wav,mp3,ogg,aiff????
Next Topic:	Filtering an ArrayCtrl

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat May 30 06:35:11 GMT+2 2026

Total time taken to generate the page: 0.00758 seconds