tag:blogger.com,1999:blog-7742435659113733626.post2612581493111802562..comments2023-06-16T06:34:15.956-06:00Comments on Nokia Carbide.c++ on Eclipse: CDT-EDC Where is the Exit?Ken Ryallhttp://www.blogger.com/profile/13632672249607934353noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-7742435659113733626.post-9739181856488522712014-11-18T05:32:59.098-06:002014-11-18T05:32:59.098-06:00Thanks for your ideas. You can also find the detai...Thanks for your ideas. You can also find the details on Affity Solutions, at the <a href="http://www.affitysolutions.com/training.htm" rel="nofollow">C Developers</a>. The main object of the Affity Solutions is to provide quality web services and is among the few software development company in Nagpur.Anonymoushttps://www.blogger.com/profile/13244324408180386775noreply@blogger.comtag:blogger.com,1999:blog-7742435659113733626.post-6478590424263195822010-09-14T03:04:29.679-06:002010-09-14T03:04:29.679-06:00I have no problem with the described behavior.You ...I have no problem with the described behavior.You can always switch to Disassembly view if you are confused by it :-) I've seen worse :-) For sure it's a bug in a compiler (gcc?), but I doubt that it will be changed/fixed.Unknownhttps://www.blogger.com/profile/08500795036326984924noreply@blogger.comtag:blogger.com,1999:blog-7742435659113733626.post-63763897800522381532010-09-08T07:09:52.618-06:002010-09-08T07:09:52.618-06:00Really the problem is that the compiler isn't ...Really the problem is that the compiler isn't doing what it's been told. No optimization should mean... NO OPTIMIZATION! I'd be filing a bug against the compiler.Chris Recoskiehttps://www.blogger.com/profile/07837602715087138014noreply@blogger.comtag:blogger.com,1999:blog-7742435659113733626.post-29195366734957258272010-09-08T03:29:42.630-06:002010-09-08T03:29:42.630-06:00I like the idea of a hint which explains what is g...I like the idea of a hint which explains what is going on, but to stick to the right behaviour. At the end of the day, this is probably just one case where the debugger behaves unexpectedly because of compiler optimization. The question is how many of these cases can you actually detect reliably. Adrian's suggestion is workable if you can guarantee that you can identify all instances of odd behaviour. A hint is better if you need to work with heuristics which don't always hold.Unknownhttps://www.blogger.com/profile/02184261985585345963noreply@blogger.comtag:blogger.com,1999:blog-7742435659113733626.post-40780749656366354952010-09-07T21:30:41.183-06:002010-09-07T21:30:41.183-06:00In this situation, I think it's perfectly just...In this situation, I think it's perfectly justified to have a configuration option in the Debugger preferences. One simple binary checkbox adds a whole lot of value here.Adrian Petrescuhttps://www.blogger.com/profile/11243791509416319614noreply@blogger.comtag:blogger.com,1999:blog-7742435659113733626.post-29300556306943879192010-09-07T18:43:06.397-06:002010-09-07T18:43:06.397-06:00Give me the exact behavior, but if you detect some...Give me the exact behavior, but if you detect something funny like this, pop up a disableable dialog explaining what is going on.Heathhttps://www.blogger.com/profile/16219966444108277892noreply@blogger.com