Be sure you look at the complete stack crawl -- there will often be one or more "caused by" clauses, showing where inner exceptions were thrown before being caught by the framework (and rethrown). So your actual application code may be buried down after a "caused by:" line.
If there are absolutely no lines of your app's code in the stack crawl, then either your app is doing something that is causing the framework to throw an exception after returning from its code, or you are just hitting a bug in the framework. Either way, supplying the actual full error and stack crawl that is being printed to the log is needed to be able to help you further.
Also as far as DDMS vs. logcat -- the DDMS output view is just another client of the same log, showing the same information as "logcat" just formatted a little differently (and with interactive filtering options etc).