On 01/22/2016 01:31 PM, Nicolai Hess wrote:
I think this is a problem of the way nautilus adds a breakpoint for
debugging the test.
(source code and byte code aren't in sync).
opened bug report 17455
werner
On 01/22/2016 01:31 PM, Nicolai Hess wrote:
I think this is a problem of the way nautilus adds a breakpoint for
debugging the test.
(source code and byte code aren't in sync).
ah, i understand
werner
2016-01-22 13:26 GMT+01:00 Werner Kassens :
> On 01/22/2016 01:16 PM, Tudor Girba wrote:
>
> I do not understand this one. Could you describe more specifically the
>> scenario?
>>
>
> if i do a "debug test" in the contextmenu of "testGenericCharCall" (in
> FFIPluginTests) and press "restart" then
On 01/22/2016 01:16 PM, Tudor Girba wrote:
I do not understand this one. Could you describe more specifically the scenario?
if i do a "debug test" in the contextmenu of "testGenericCharCall" (in
FFIPluginTests) and press "restart" then "= 130" is highlighted.
werner
Hi,
> On Jan 22, 2016, at 12:53 PM, Werner Kassens wrote:
>
> On 01/22/2016 11:48 AM, Tudor Girba wrote:
>> Hi,
>>
>> Yes. That is the type of input that we need.
>>
>> It would be great if others would do the same.
>
> Hi Doru,
> ok, i often use the debugger to test that some code actually d
On 01/22/2016 11:48 AM, Tudor Girba wrote:
Hi,
Yes. That is the type of input that we need.
It would be great if others would do the same.
Hi Doru,
ok, i often use the debugger to test that some code actually does what i
intended:
in the old one i click first on "stack top" and then click th
Hi,
Yes. That is the type of input that we need.
It would be great if others would do the same.
Cheers,
Doru
> On Jan 22, 2016, at 11:42 AM, stepharo wrote:
>
> Hi guys
>
> Many of you may bthink that I'm mad or whatever about new UI elements.
> Sometimes this is true :)
> but most of the
