[Pharo-dev] Debugger "reporting" feature

Stephane Ducasse stepharo.self at gmail.com
Thu Nov 2 13:03:58 EDT 2017


Can you open a bug entry?

On Thu, Nov 2, 2017 at 4:16 PM, Ben Coman <btc at openinworld.com> wrote:
> sounds good.
> cheers -ben
>
> On Thu, Nov 2, 2017 at 10:55 PM, Denis Kudriashov <dionisiydk at gmail.com>
> wrote:
>>
>> Maybe we should name and implement it as "copy stack to clipboard"?
>>
>> 2017-11-02 13:19 GMT+01:00 Ben Coman <btc at openinworld.com>:
>>>
>>> I've never used it to auto-report to any remote remote server. That part
>>> can go.
>>> But as I stated, I do find it useful for getting a text representation of
>>> the stack for manually pasting into fogbugz issues, instead of having to dig
>>> through the halos into the morph contents.
>>> Can this part be kept and moved into the stack-context-menu?
>>>
>>> cheers -ben
>>>
>>> On Thu, Nov 2, 2017 at 5:59 PM, Denis Kudriashov <dionisiydk at gmail.com>
>>> wrote:
>>>>
>>>> I think it is outdated feature and we should remove it to not confuse
>>>> people.
>>>>
>>>> 2017-11-02 9:10 GMT+01:00 Peter Uhnák <i.uhnak at gmail.com>:
>>>>>
>>>>> Is this functionality actuaat part can golly used? Where do the reports
>>>>> end up? What is contained in the report?
>>>>>
>>>>> Peter
>>>>>
>>>>> On Thu, Nov 2, 2017 at 4:35 AM, Ben Coman <btc at openinworld.com> wrote:
>>>>>>
>>>>>> In the Pre-Debug window there is the <Report> button that coverts the
>>>>>> call stack to text that can be pasted into an email.  But when you proceed
>>>>>> into the main debugger it seems you lose access to that feature.
>>>>>>
>>>>>> Would it be worth adding <Report> to the debugger context menu?
>>>>>>
>>>>>> cheers -ben
>>>>>
>>>>>
>>>>
>>>
>>
>




More information about the Pharo-dev mailing list