Re: [Lldb-commits] [PATCH] D37651: Fix for bug 34532 - A few rough corners related to post-mortem debugging (core/minidump)

Sure, but reading a core file involves handling user input. Obviously that has to be sanitized and you can't crash on user input. I don't think there's ever been any disagreement about that. On the other hand, if you just type an expression in the debugger and expect an answer back, after clang

Re: [Lldb-commits] [PATCH] D37651: Fix for bug 34532 - A few rough corners related to post-mortem debugging (core/minidump)

I think we are talking at cross purposes. Seems to me you are saying “If we can assert that the answers to questions I ask must always copacetic, then we can express that in software, and that will make things so much easier". I’m saying "my experience of the data debuggers have to deal with

Re: [Lldb-commits] [PATCH] D37651: Fix for bug 34532 - A few rough corners related to post-mortem debugging (core/minidump)

On Sat, Sep 9, 2017 at 12:04 PM Jim Ingham wrote: > > I disagree here. If you can reasonably unwind from an error you should do > so even if you can’t figure out how you could have gotten an answer you > didn’t expect. If an API is returning a pointer to something you should

Re: [Lldb-commits] [PATCH] D37651: Fix for bug 34532 - A few rough corners related to post-mortem debugging (core/minidump)

On Sat, Sep 9, 2017 at 11:18 AM Jim Ingham wrote: > On Sep 8, 2017, at 11:45 PM, Zachary Turner wrote: > > On Fri, Sep 8, 2017 at 8:19 PM Jason Molenda wrote: > >> Also keep in mind that debug sessions have a tendency to be long lived.

Re: [Lldb-commits] [PATCH] D37651: Fix for bug 34532 - A few rough corners related to post-mortem debugging (core/minidump)

On Fri, Sep 8, 2017 at 8:19 PM Jason Molenda wrote: > Also keep in mind that debug sessions have a tendency to be long lived. I > may be working through a problem for half an hour -- or this may be the one > rare instance where a bug reproduces -- and crashing because some