Smalltalk › Frameworks & Tools › Moose

Problem with GTDebugger...

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

7 messages Options

abergel

Problem with GTDebugger...

What can I do with that?

I have just downloaded the latest moose 6.0 image, and evaluating “Deprecation signal” leads to an emergency debugger.

How comes that the system is so unstable. This is puzzling me.

I will not use the Moose image anymore.

Alexandre

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Peter Uhnak

Re: Problem with GTDebugger...

I've encountered it 10 minutes ago, seems like the debugger is deprecated?

As a dirty quick fix you can do

~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Deprecation raiseWarning: false

~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Peter

On Fri, Sep 4, 2015 at 11:33 PM, Alexandre Bergel <[hidden email]> wrote:

What can I do with that?

I have just downloaded the latest moose 6.0 image, and evaluating “Deprecation signal” leads to an emergency debugger.

How comes that the system is so unstable. This is puzzling me.

I will not use the Moose image anymore.

Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

abergel

Re: Problem with GTDebugger...

Well, the problem is caused by the debugger. Evaluating “Error signal” produces the same result :-(

Alexandre

> On Sep 4, 2015, at 6:37 PM, Peter Uhnák <[hidden email]> wrote:
>
> I've encountered it 10 minutes ago, seems like the debugger is deprecated?
>
> As a dirty quick fix you can do
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Deprecation raiseWarning: false
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Peter
>
> On Fri, Sep 4, 2015 at 11:33 PM, Alexandre Bergel <[hidden email]> wrote:
> What can I do with that?
>
> I have just downloaded the latest moose 6.0 image, and evaluating “Deprecation signal” leads to an emergency debugger.
>
> <Screen Shot 2015-09-04 at 6.31.45 PM.png>
>
> How comes that the system is so unstable. This is puzzling me.
>
> I will not use the Moose image anymore.
>
> Alexandre
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Andrei Chis

Re: Problem with GTDebugger...

I committed a fix.

Can you try if the next moose build fixes the problem.

Cheers,

Andrei

On Fri, Sep 4, 2015 at 11:41 PM, Alexandre Bergel <[hidden email]> wrote:

Well, the problem is caused by the debugger. Evaluating “Error signal” produces the same result :-(

Alexandre

> On Sep 4, 2015, at 6:37 PM, Peter Uhnák <[hidden email]> wrote:
>
> I've encountered it 10 minutes ago, seems like the debugger is deprecated?
>
> As a dirty quick fix you can do
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Deprecation raiseWarning: false
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Peter
>
> On Fri, Sep 4, 2015 at 11:33 PM, Alexandre Bergel <[hidden email]> wrote:
> What can I do with that?
>
> I have just downloaded the latest moose 6.0 image, and evaluating “Deprecation signal” leads to an emergency debugger.
>
> <Screen Shot 2015-09-04 at 6.31.45 PM.png>

>
> How comes that the system is so unstable. This is puzzling me.
>
> I will not use the Moose image anymore.
>
> Alexandre
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Nicolai Hess

Re: Problem with GTDebugger...

In reply to this post by abergel

on:send:to:

was deprecated. The debugger should use

when:send:to:

(I always wonder why all the GL-Tools/classes inherit from Announcer, and btw

isn't it bad to register self for announces send by self?)

registerActions

self on: GLMBrowserClosing send: #actOnBrowserClosing: to: self.
self on: DebugActionExecuted send: #updateBrowser to: self.

2015-09-04 23:33 GMT+02:00 Alexandre Bergel <[hidden email]>:

What can I do with that?

I have just downloaded the latest moose 6.0 image, and evaluating “Deprecation signal” leads to an emergency debugger.

How comes that the system is so unstable. This is puzzling me.

I will not use the Moose image anymore.

Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

abergel

Re: Problem with GTDebugger...

In reply to this post by Andrei Chis

Thanks Andrei!
Seems to work now…

Alexandre

> On Sep 4, 2015, at 6:55 PM, Andrei Chis <[hidden email]> wrote:
>
> I committed a fix.
> Can you try if the next moose build fixes the problem.
>
> Cheers,
> Andrei
>
> On Fri, Sep 4, 2015 at 11:41 PM, Alexandre Bergel <[hidden email]> wrote:
> Well, the problem is caused by the debugger. Evaluating “Error signal” produces the same result :-(
>
> Alexandre
>
>
> > On Sep 4, 2015, at 6:37 PM, Peter Uhnák <[hidden email]> wrote:
> >
> > I've encountered it 10 minutes ago, seems like the debugger is deprecated?
> >
> > As a dirty quick fix you can do
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > Deprecation raiseWarning: false
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >
> > Peter
> >
> > On Fri, Sep 4, 2015 at 11:33 PM, Alexandre Bergel <[hidden email]> wrote:
> > What can I do with that?
> >
> > I have just downloaded the latest moose 6.0 image, and evaluating “Deprecation signal” leads to an emergency debugger.
> >
> > <Screen Shot 2015-09-04 at 6.31.45 PM.png>
> >
> > How comes that the system is so unstable. This is puzzling me.
> >
> > I will not use the Moose image anymore.
> >
> > Alexandre
> > --
> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> > Alexandre Bergel http://www.bergel.eu
> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> >
> >
> >
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
> >
> >
> > _______________________________________________
> > Moose-dev mailing list
> > [hidden email]
> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

abergel

Re: Problem with GTDebugger...

In reply to this post by Nicolai Hess

> on:send:to:
> was deprecated. The debugger should use
> when:send:to:

Yesterday evening I committed the Roassal2 integration in Glamour. But I did not check all sender.

> (I always wonder why all the GL-Tools/classes inherit from Announcer, and btw
> isn't it bad to register self for announces send by self?)

Me too. I discussed about this point with Doru some time ago. Apparently this is something central to Glamour.

Alexandre

>
> registerActions
>
> self on: GLMBrowserClosing send: #actOnBrowserClosing: to: self.
> self on: DebugActionExecuted send: #updateBrowser to: self.
>
>
>
> 2015-09-04 23:33 GMT+02:00 Alexandre Bergel <[hidden email]>:
> What can I do with that?
>
> I have just downloaded the latest moose 6.0 image, and evaluating “Deprecation signal” leads to an emergency debugger.
>
> <Screen Shot 2015-09-04 at 6.31.45 PM.png>
>
> How comes that the system is so unstable. This is puzzling me.
>
> I will not use the Moose image anymore.
>
> Alexandre
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev