problem with debugger

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

problem with debugger

Fabrizio Perin-3
Hi,
i'm using the image 10392. When I try to debug something an error occurred every time I hit a button (like debug for instance). The error is "Error: key not found". There is a way to copy the stack?

Thanks a lot,
Fabrizio

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: problem with debugger

Marcus Denker-3

On 27.07.2009, at 10:06, Fabrizio Perin wrote:

> Hi,
> i'm using the image 10392. When I try to debug something an error  
> occurred every time I hit a button (like debug for instance). The  
> error is "Error: key not found". There is a way to copy the stack?
>

Hi Fabrizio,

The last updates introduces a bug. I will do an update soon to fix  
that (see bugtracker).

        Marcus




--
Marcus Denker - http://marcusdenker.de
PLEIAD Lab - Computer Science Department (DCC) - University of Chile


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: problem with debugger

Mariano Martinez Peck
In reply to this post by Fabrizio Perin-3


2009/7/27 Fabrizio Perin <[hidden email]>
Hi,
i'm using the image 10392. When I try to debug something an error occurred every time I hit a button (like debug for instance). The error is "Error: key not found". There is a way to copy the stack?

I don't know if I understood your question, but perhaps you might want to see PharoDebug.log in the directory where your image is. There you will have all the stacktrace.

Best,

Mariano

 

Thanks a lot,
Fabrizio

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: problem with debugger

Damien Cassou
In reply to this post by Fabrizio Perin-3
Hi Fabrizio,

2009/7/27 Fabrizio Perin <[hidden email]>:
> i'm using the image 10392. When I try to debug something an error occurred
> every time I hit a button (like debug for instance). The error is "Error:
> key not found". There is a way to copy the stack?

this is a known bug which has a fix. Please find more information on:

http://code.google.com/p/pharo/issues/detail?id=913

To load the fix, open the PharoInbox repository using Monticello and
load Compiler-damiencassou.115.

Sorry about that.

--
Damien Cassou
http://damiencassou.seasidehosting.st

"Lambdas are relegated to relative obscurity until Java makes them
popular by not having them." James Iry

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: problem with debugger

Marcus Denker-3

On 27.07.2009, at 10:12, Damien Cassou wrote:

> Hi Fabrizio,
>
> 2009/7/27 Fabrizio Perin <[hidden email]>:
>> i'm using the image 10392. When I try to debug something an error  
>> occurred
>> every time I hit a button (like debug for instance). The error is  
>> "Error:
>> key not found". There is a way to copy the stack?
>
> this is a known bug which has a fix. Please find more information on:
>
> http://code.google.com/p/pharo/issues/detail?id=913
>
> To load the fix, open the PharoInbox repository using Monticello and
> load Compiler-damiencassou.115.
>
> Sorry about that.
>

#10393 should fix this and the encoding bug.

        Marcus




--
Marcus Denker - http://marcusdenker.de
PLEIAD Lab - Computer Science Department (DCC) - University of Chile


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: problem with debugger

Fabrizio Perin-3
thanks a lot. You were amazingly helpful :)

I will download the next upgrade and next time I will provide you a better feed back.

Cheers,
Fabrizio

2009/7/27 Marcus Denker <[hidden email]>

On 27.07.2009, at 10:12, Damien Cassou wrote:

> Hi Fabrizio,
>
> 2009/7/27 Fabrizio Perin <[hidden email]>:
>> i'm using the image 10392. When I try to debug something an error
>> occurred
>> every time I hit a button (like debug for instance). The error is
>> "Error:
>> key not found". There is a way to copy the stack?
>
> this is a known bug which has a fix. Please find more information on:
>
> http://code.google.com/p/pharo/issues/detail?id=913
>
> To load the fix, open the PharoInbox repository using Monticello and
> load Compiler-damiencassou.115.
>
> Sorry about that.
>

#10393 should fix this and the encoding bug.

       Marcus




--
Marcus Denker - http://marcusdenker.de
PLEIAD Lab - Computer Science Department (DCC) - University of Chile


_______________________________________________


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project