Re: [Pharo-dev] Debugging red screen

[Natalia Tymchuk]

Thanks a lot for all.
> 
> It is also possible to see Trachel classes involved, so maybe there is a 
> problem with some Roassal code.

Yes, it is. I will write a letter on moose-dev list about it.


>> did you try to bring up the halo menu and select "debug drawing error”?
 
Thanks, it works. Now I will know what to do in similar situations.

>> This error looks like AthensCairoMatrix translateBy is called with wrong 
>> argument type.
>> This may happen if it is called with a fraction instead of a float type.

Yes, that was exactly the problem.

Thanks.

Best regards,
Natalia

Re: [Pharo-dev] Debugging red screen

[Alejandro Infante]

Hi,
It is also possible to see Trachel classes involved, so maybe there is a 
problem with some Roassal code.

Do you have some way to reproduce it??

Cheers,
Alejandro

> On Mar 11, 2015, at 4:11 PM, Tudor Girba  wrote:
> 
> Hi,
> 
> I think the problem is that your Pharo30.sources are not available. Could it 
> be?
> 
> Cheers,
> Doru
> 
> 
> 
> On Wed, Mar 11, 2015 at 7:26 PM, Nicolai Hess  > wrote:
> Hi Natalia,
> 
> did you try to bring up the halo menu and select "debug drawing error"?
> 
> This error looks like AthensCairoMatrix translateBy is called with wrong 
> argument type.
> This may happen if it is called with a fraction instead of a float type.
> 
> nicolai
> 
> 
> 2015-03-11 17:15 GMT+01:00 Natalia Tymchuk  >:
> Hello.
> I’m working with graphics. Usually if i have some problem I got the debugger 
> window, however some times it gives me the red rectangle error. I cannot 
> understand from it what is the problem.
> What should I do in such case, maybe there is some way to get this 
> signalError in debugger?
> 
> Best regards,
> Natalia
> 
> P.S. Here I attach the error I got.
> 
>  
> 
> 
> 
> 
> 
> 
> -- 
> www.tudorgirba.com 
> 
> "Every thing has its own flow"

Re: [Pharo-dev] Debugging red screen

[Peter Uhnák]

Also I believe someone named it the "Red Screen of Death".

On Wed, Mar 11, 2015 at 5:39 PM, Peter Uhnák  wrote:

> I've seen this many times when I had an error in my Athens drawing or were
> performing illegal operation in drawDuring: [...] (or the canvas wasn't
> initialized or whatever).
> Unfortunately I don't know how to open proper debugger... I always found
> the issue with "self halt."s. :(
>
> Peter
>
> On Wed, Mar 11, 2015 at 5:24 PM, Max Leske  wrote:
>
>>
>> > On 11 Mar 2015, at 17:15, Natalia Tymchuk <
>> natalia.tymc...@unikernel.net> wrote:
>> >
>> > Hello.
>> > I’m working with graphics. Usually if i have some problem I got the
>> debugger window, however some times it gives me the red rectangle error. I
>> cannot understand from it what is the problem.
>> > What should I do in such case, maybe there is some way to get this
>> signalError in debugger?
>> >
>> > Best regards,
>> > Natalia
>>
>> I work with NB too and I’ve never seen that (I either get a debugger or
>> my image crashes :) ). Maybe it has something to do with the fact that
>> you’re using / modifying Athens which is itself used to render elements of
>> the image?
>>
>> Cheers,
>> Max
>>
>> >
>> > P.S. Here I attach the error I got.
>> >
>> >  
>> >
>> >
>>
>>
>>
>

Re: [Pharo-dev] Debugging red screen

[Peter Uhnák]

I've seen this many times when I had an error in my Athens drawing or were
performing illegal operation in drawDuring: [...] (or the canvas wasn't
initialized or whatever).
Unfortunately I don't know how to open proper debugger... I always found
the issue with "self halt."s. :(

Peter

On Wed, Mar 11, 2015 at 5:24 PM, Max Leske  wrote:

>
> > On 11 Mar 2015, at 17:15, Natalia Tymchuk 
> wrote:
> >
> > Hello.
> > I’m working with graphics. Usually if i have some problem I got the
> debugger window, however some times it gives me the red rectangle error. I
> cannot understand from it what is the problem.
> > What should I do in such case, maybe there is some way to get this
> signalError in debugger?
> >
> > Best regards,
> > Natalia
>
> I work with NB too and I’ve never seen that (I either get a debugger or my
> image crashes :) ). Maybe it has something to do with the fact that you’re
> using / modifying Athens which is itself used to render elements of the
> image?
>
> Cheers,
> Max
>
> >
> > P.S. Here I attach the error I got.
> >
> >  
> >
> >
>
>
>

Re: [Pharo-dev] Debugging red screen

[kilon alios]

I have seen that myself but I dont think it was NB , I think it was
strikefonts and TTFs but that problem has been resolved since then. So its
possible to get severe red box of doom. Fortunately it rarely happens and
has happened to me 1-2 times.

On Wed, Mar 11, 2015 at 6:24 PM, Max Leske  wrote:

>
> > On 11 Mar 2015, at 17:15, Natalia Tymchuk 
> wrote:
> >
> > Hello.
> > I’m working with graphics. Usually if i have some problem I got the
> debugger window, however some times it gives me the red rectangle error. I
> cannot understand from it what is the problem.
> > What should I do in such case, maybe there is some way to get this
> signalError in debugger?
> >
> > Best regards,
> > Natalia
>
> I work with NB too and I’ve never seen that (I either get a debugger or my
> image crashes :) ). Maybe it has something to do with the fact that you’re
> using / modifying Athens which is itself used to render elements of the
> image?
>
> Cheers,
> Max
>
> >
> > P.S. Here I attach the error I got.
> >
> >  
> >
> >
>
>
>

Re: [Pharo-dev] Debugging red screen

[Max Leske]

> On 11 Mar 2015, at 17:15, Natalia Tymchuk  
> wrote:
> 
> Hello.
> I’m working with graphics. Usually if i have some problem I got the debugger 
> window, however some times it gives me the red rectangle error. I cannot 
> understand from it what is the problem.
> What should I do in such case, maybe there is some way to get this 
> signalError in debugger?
> 
> Best regards,
> Natalia

I work with NB too and I’ve never seen that (I either get a debugger or my 
image crashes :) ). Maybe it has something to do with the fact that you’re 
using / modifying Athens which is itself used to render elements of the image?

Cheers,
Max

> 
> P.S. Here I attach the error I got.
> 
>  
> 
>