Updated Issue987 with a SLICE in Inbox, which "fixes" the DNU in the  
way below.
Used printString instead of asString as proposed by Hernán, as it (in  
principle) should be more robustly implemented and thus more suited  
for debugger display.
(If sig's idea from some time back was adopted, this should be  
debugString instead of printString, of course).

Cheers,
Henry

On Oct 5, 2009, at 11:51 23AM, Henrik Johansen wrote:

> For the stack top error, a better solution than adding asText to
> Object would be to implement:
> ContextVariablesInspector >> contents
>       ^super contents printString
>
> It's a subclass of StringHolder for some reason, which explain why it
> doesn't exactly like that the ContextVariable can be any arbitrary
> object...
>
> Cheers,
> Henry
>
> On Oct 5, 2009, at 11:17 33AM, Hernán Morales Durand wrote:
>
>> Hi Ramiro,
>> You don't need to modify a method to open a debugger, hitting Alt +
>> . will do it. The behavior you describe is present in Pharo-Core
>> #10466 too and is probably the same when clicking the "stack top"  
>> item
>> in the Debugger right bottom pane (the context variables inspector).
>> I'm not fan at all of populating Object, but a quick workaround for
>> those who want to continue debugging without meta-debugging is to
>> define in Object
>>
>> asText
>>      ^ self asString asText
>>
>> Cheers,
>>
>> Hernán
>>
>> 2009/10/5 Ramiro Diaz Trepat <ram...@diaztrepat.name>:
>>> Sorry, and the way to reproduce was simply introducing a "self
>>> halt" in some
>>> method, or executing over a real bug as well, and trying to debug
>>> from
>>> there.
>>> Thanks again
>>>
>>>
>>> On Mon, Oct 5, 2009 at 8:47 AM, Ramiro Diaz Trepat <ram...@diaztrepat.name
>>>>
>>> wrote:
>>>>
>>>> Hi Damien, thanks for answering.
>>>> The error happens on a the previous dev image (09.09.03) that was
>>>> updated
>>>> until yesterday night.
>>>> If I download the new dev image though, the error seems to go away.
>>>> I thought there was no difference, in theory at least, between an
>>>> updated
>>>> image and a freshly downloaded one.
>>>> Cheers
>>>>
>>>> r.
>>>>
>>>>
>>>> On Mon, Oct 5, 2009 at 12:41 AM, Damien Cassou <damien.cas...@gmail.com
>>>>>
>>>> wrote:
>>>>>
>>>>> 2009/10/4 Ramiro Diaz Trepat <ram...@diaztrepat.name>:
>>>>>> I saw previous posts from Steph saying that this fix had already
>>>>>> been
>>>>>> pushed, but I have an image updated up to now and it does happen.
>>>>>
>>>>> Please provide a detailed process on how to reproduce. Telling us
>>>>> the
>>>>> image you used is of interest too.
>>>>>
>>>>> --
>>>>> 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
>>>>> Pharo-project@lists.gforge.inria.fr
>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- 
>>>>> project
>>>>
>>>
>>>
>>> _______________________________________________
>>> Pharo-project mailing list
>>> Pharo-project@lists.gforge.inria.fr
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> Pharo-project@lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>


_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to