Anything exception that is done by the implementation in order to implement normally stopping at the entry point should be covered up and not sent to the user. A thread has the notion of a private stop info and one that is produced for the public consumption. If this exception is indeed only showing up because this is the way we were able to stop at the entry point, we should not be showing that to the user.
> On Mar 18, 2016, at 11:24 AM, Carlo Kok via lldb-dev > <lldb-dev@lists.llvm.org> wrote: > > When starting a process on Win32 there's an internal exception (breakpint) > that leaks to the debug caller: > s 'Exception 0x80000003 encountered at address 0x7789ccbc'#0 > > This one is dealt with by the debugger internally but there's still a > StateType.eStateStopped event for it. On other platforms there's no exception > like this for the internal start breakpoint (note that actual breakpoints > after this hit just fine) > > -- > Carlo Kok > RemObjects Software > _______________________________________________ > lldb-dev mailing list > lldb-dev@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev _______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
