[lldb-dev] break on exceptions/windows
Jim Ingham via lldb-dev
lldb-dev at lists.llvm.org
Mon Apr 4 10:23:46 PDT 2016
The exception breakpoints Greg is talking about are language exceptions (C++ throws, Swift Errors and the like.)
I don't know what kind of exception you are talking about here, but at least from a command interface standpoint, it would be good to keep alike things that actually are alike, but only if they ARE actually alike.
> On Apr 4, 2016, at 10:07 AM, Greg Clayton <gclayton at apple.com> wrote:
> You should talk to Jim Ingham on this. We have special exception breakpoints that we did for Swift and you will want to follow the same methodology. I am not sure what the methodology is so I'm CC'ing Jim so can can comment.
>> On Apr 4, 2016, at 9:52 AM, Zachary Turner via lldb-dev <lldb-dev at lists.llvm.org> wrote:
>> Take a look at ProcessWindowsLive.cpp in Plugins/Process/Windows. There's a function called ProcessWindowsLive::OnDebugException. If you're working in a fork and you don't intend to upstream any changes, you could just modify the default case of the switch statement there to not return ExceptionResult::SendToApplication.
>> If you wanted to upstream something, you'd probably want a way to specify what types of exceptions to break on. For this you'd need to implement a new command so that you could do something like "break set --exception 0xC0000005" and pass that information to the ProcessWindowsLive plugin somehow, so that it could decide when to break and when to pass it on to the application for a second chance.
>> On Mon, Apr 4, 2016 at 8:26 AM Carlo Kok <ck at remobjects.com> wrote:
>> Op 2016-04-04 om 16:00 schreef Zachary Turner:
>>> Not possible currently, although it wouldn't be too hard to add. Would
>>> be a welcome feature if you are interested
>> I'm (obviously?) interested. But wouldn't know where to start.
>> Carlo Kok
>> RemObjects Software
>> lldb-dev mailing list
>> lldb-dev at lists.llvm.org
More information about the lldb-dev