U++ forum: Welcome to the forum

Status & Roadmap

Authors & License

Funding Ultimate++

Search on this site

Search in forums

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

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

Return to the default flat view

Create a new topic

Submit Reply

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

Fri, 12 July 2019 00:46

Novo is currently offline

Novo
Messages: 1358
Registered: December 2006

Ultimate Contributor

mirek wrote on Thu, 11 July 2019 18:15

I believe you are wrong. I believe Ctrl+C is equivalent of calling exit(). In that case, global variables get destructed, but local variables do not. This is also quite clear for the implementation of signals - they are asynchronouse and thus do not have to use the same stack so no stack unwinding is possible.

BTW, destructing global variables is the mechanism used to activate the leak checker

Mirek

I saw that MemDiagCls is a global static ...
Let's say only global statics get destroyed, and stack doesn't get unwinded. In such case every time you press CTRL-C you should get memory leaks. But this never happens to my apps ... BTW, info for stack unwinding is always included into app, especially when you compile it with exception support (this is related to x64 Win and POSIX ABI).

"no stack unwinding is possible" - try to run an app with gdb and press CTRL-C. gdb will stop each thread in your app and will show you call stacks for each thread. Call stack for each thread can we unwinded, IMHO ...

This is my understanding of this process ...

Regards,
Novo

Report message to a moderator

Send a private message to this user

[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) ] [

] [

PDF

]

Current Time: Thu Apr 25 17:30:35 CEST 2024

Total time taken to generate the page: 0.02778 seconds