On Fri, Jun 2, 2017 at 8:08 AM, Eliot Miranda
wrote:
> Hi Guille,
>
> On Wed, May 31, 2017 at 12:48 AM, Guillermo Polito <
> guillermopol...@gmail.com> wrote:
>
>>
>>
>> On Mon, May 29, 2017 at 6:07 PM, Eliot Miranda
>> wrote:
>>
>>> Hi Thomas,
Thanks eliot. I really think that pushing the debugger to the next level is
an exciting perspective and I'm super happy that thomas accepted my crazy
topics.
Stef
On Fri, Jun 2, 2017 at 2:08 AM, Eliot Miranda
wrote:
> Hi Guille,
>
> On Wed, May 31, 2017 at 12:48 AM,
Hi Guille,
On Wed, May 31, 2017 at 12:48 AM, Guillermo Polito <
guillermopol...@gmail.com> wrote:
>
>
> On Mon, May 29, 2017 at 6:07 PM, Eliot Miranda
> wrote:
>
>> Hi Thomas,
>>
>>
>> On May 29, 2017, at 7:41 AM, Ben Coman wrote:
>>
>>
>>
>> On
On Mon, May 29, 2017 at 6:07 PM, Eliot Miranda
wrote:
> Hi Thomas,
>
>
> On May 29, 2017, at 7:41 AM, Ben Coman wrote:
>
>
>
> On Mon, May 29, 2017 at 9:34 PM, wrote:
>
> [...]
>
>> Here is my example code. Beware,
Hi Thomas,
> On May 29, 2017, at 7:41 AM, Ben Coman wrote:
>
>
>
>> On Mon, May 29, 2017 at 9:34 PM, wrote:
>> Hi,
>>
>> I'm working with DebugSession to see if I can implement something that would
>> step into an execution until a given
On Mon, May 29, 2017 at 9:34 PM, wrote:
> Hi,
>
> I'm working with DebugSession to see if I can implement something that
> would step into an execution until a given expression evaluates to a
> different value than the value it had at the beginning to quickly
Hi,
I'm working with DebugSession to see if I can implement something that
would step into an execution until a given expression evaluates to a
different value than the value it had at the beginning to quickly
localise the precise point where an invariant is broken.
But it appears that