<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.newlc.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>NewLC - Carbide + S60 SDK: How to see the call stack - Comments</title>
 <link>http://www.newlc.com/en/topic-16406</link>
 <description>Comments for &quot;Carbide + S60 SDK: How to see the call stack&quot;</description>
 <language>en</language>
<item>
 <title>Re: Carbide + S60 SDK: How to catch unhandled exceptions?</title>
 <link>http://www.newlc.com/en/topic-16406#comment-35258</link>
 <description>&lt;div class=&quot;smf-content&quot;&gt;OK - now I got to the point of actually getting the tread-in-question to halt.&lt;br /&gt;&lt;br /&gt;How do I get the call-stack readable. Or at least get more info on the stack frame so I can see some pointers etc that must be present in a debug build I am using.&lt;br /&gt;Friend of mine I discussed this with said that the problem could be resolved by using CodeWarrior as well.&lt;br /&gt;&lt;br /&gt;&lt;/div&gt;</description>
 <pubDate>Wed, 18 Oct 2006 13:21:31 +0200</pubDate>
 <dc:creator>mteppo</dc:creator>
 <guid isPermaLink="false">comment 35258 at http://www.newlc.com</guid>
</item>
<item>
 <title>Carbide + S60 SDK: How to see the call stack</title>
 <link>http://www.newlc.com/en/topic-16406</link>
 <description>&lt;div class=&quot;smf-content&quot;&gt;&lt;/div&gt;&lt;p&gt;&lt;a href=&quot;http://www.newlc.com/en/topic-16406&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.newlc.com/en/topic-16406#comments</comments>
 <category domain="http://www.newlc.com/en/forums/carbide-eclipse">Carbide.c++</category>
 <pubDate>Wed, 18 Oct 2006 08:21:50 +0200</pubDate>
 <dc:creator>mteppo</dc:creator>
 <guid isPermaLink="false">16061 at http://www.newlc.com</guid>
</item>
</channel>
</rss>
