Smalltalk › Pharo › Pharo Smalltalk Developers

Debugger "reporting" feature

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

8 messages Options

Ben Coman

Debugger "reporting" feature

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

Peter Uhnak

Re: Debugger "reporting" feature

Is this functionality actually 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 <[hidden email]> 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

Denis Kudriashov

Re: Debugger "reporting" feature

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 <[hidden email]>:

Is this functionality actually 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 <[hidden email]> 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

Ben Coman

Re: Debugger "reporting" feature

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 <[hidden email]> 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 <[hidden email]>:
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 <[hidden email]> 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

Denis Kudriashov

Re: Debugger "reporting" feature

Maybe we should name and implement it as "copy stack to clipboard"?

2017-11-02 13:19 GMT+01:00 Ben Coman <[hidden email]>:

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 <[hidden email]> 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 <[hidden email]>:
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 <[hidden email]> 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

Ben Coman

Re: Debugger "reporting" feature

sounds good.

cheers -ben

On Thu, Nov 2, 2017 at 10:55 PM, Denis Kudriashov <[hidden email]> wrote:

Maybe we should name and implement it as "copy stack to clipboard"?

2017-11-02 13:19 GMT+01:00 Ben Coman <[hidden email]>:
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 <[hidden email]> 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 <[hidden email]>:
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 <[hidden email]> 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

Stephane Ducasse-3

Re: Debugger "reporting" feature

Can you open a bug entry?

On Thu, Nov 2, 2017 at 4:16 PM, Ben Coman <[hidden email]> wrote:

> sounds good.
> cheers -ben
>
> On Thu, Nov 2, 2017 at 10:55 PM, Denis Kudriashov <[hidden email]>
> wrote:
>>
>> Maybe we should name and implement it as "copy stack to clipboard"?
>>
>> 2017-11-02 13:19 GMT+01:00 Ben Coman <[hidden email]>:
>>>
>>> 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 <[hidden email]>
>>> 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 <[hidden email]>:
>>>>>
>>>>> 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 <[hidden email]> 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
>>>>>
>>>>>
>>>>
>>>
>>
>

Ben Coman

Re: Debugger "reporting" feature

cool. done.

https://pharo.fogbugz.com/f/cases/20631/debugger-copy-stack-to-clipboard

cheers -ben

On Fri, Nov 3, 2017 at 1:03 AM, Stephane Ducasse <[hidden email]> wrote:

Can you open a bug entry?

On Thu, Nov 2, 2017 at 4:16 PM, Ben Coman <[hidden email]> wrote:
> sounds good.
> cheers -ben
>
> On Thu, Nov 2, 2017 at 10:55 PM, Denis Kudriashov <[hidden email]>
> wrote:
>>
>> Maybe we should name and implement it as "copy stack to clipboard"?
>>
>> 2017-11-02 13:19 GMT+01:00 Ben Coman <[hidden email]>:
>>>
>>> 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 <[hidden email]>
>>> 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 <[hidden email]>:
>>>>>
>>>>> 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 <[hidden email]> 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
>>>>>
>>>>>
>>>>
>>>
>>
>