[squeak-dev] Re: About controlling debugger popping up
Andreas Raab
andreas.raab at gmx.de
Tue Aug 5 18:09:02 UTC 2008
One thing you could do is to give people a ticket id (returned from the
server) so they can check for themselves if they want to know if a
problem was fixed. It doesn't require them to reveal any info but makes
it possible to check for the status of the problem.
Also, I think the problem is merely one of convenience. If you would
pre-populate the email they'd probably be fine with it. It's just that
when people are frustrated (which they are since the system just blew up
on 'em) they're usually not in the mood to spend more time than
absolutely necessary. If it's one click, fine, if it's more, it's not.
Cheers,
- Andreas
John M McIntosh wrote:
> Well people won't give you even an email address. This unfortunate
> breaks part of the problem question answer cycle. Although we might
> push all the stacks for all the processes and most of the data values,
> that sometimes only shows: Gee how did they do that, but then you have
> no way to ask what they were doing... Suggestions on how to entice
> that information out of a user is welcome.
>
>> Cheers,
>> - Andreas
>>
>> John M McIntosh wrote:
>>> In Sophie we do exactly that, we prompt the user for permission and
>>> ask for name-address-etc, plus any other additional information.
>>>
>>> (a) many people give permission, we had to alter the stack trace-back
>>> logic to print lots more data btw. Perhaps as much as 200K of data has
>>> to come back in order to figure out why the walkback occured.
>>>
>>> (b) No one ever supplies contact information, they will anonoymously
>>> beg for help tho. Sadly anonoymous pleas for help can't be answered
>>>
>>> (c) That gets POSTed to a web site, where the server then saves and
>>> emails the Sophie Support Engineer. Obviously a bit of programming
>>> there could use a database to figure out if the error is unique or not
>>> etc. Even say to emailing the person back with a problem tracking
>>> number or existing entry
>>>
>>>>> Hello list,
>>>>>
>>>>> I was thinking how I would control the opening of debugger on deployed
>>>>> application.
>>>>> Imagine I want to copy the stack and send it by email or something like
>>>>> that.
>>>>>
>>>
>>
>>
>
>
More information about the Squeak-dev
mailing list
|