Sergey!
On what platform runs Android Device Emulator?If it is Windows you can run your emulator under debugger.Please set windbg as a postmortem debugger and try to run your app maybe debugger's break-in will be trigerred by some unhandled exception in theemulator code.You can also tryto do some investigation and find how it Launcher is implemented.For example if it is an DLL loaded by an emulator you can set a conditional breakpoint on dllmain call and single-step through the code.
Other thing you can do is to use an IDA disassembler and find the address of the string being displayed when Launcher crashes.When you have an address (probably global variable) you can set the conditional breakpoint on this address it should be some of the windowing procedures which gets string address to be displayed.From this point you can try to reconstruct the call stack simply by going through the return addresses pushed on the stack.
Btw Look for minidump file when Launcher crashes.