On 4/9/07, David Grogono <[EMAIL PROTECTED]> wrote: > On Apr 9, 2007, at 4:19 PM, Dennis Birch wrote: > > For that matter, perhaps you could clarify whether we should be > > submitting reports with screen shots of internal error alerts. I > > submitted one of those earlier with the set of steps that preceded the > > error, but I know you almost certainly won't be able to reproduce the > > error following them. Again, I'm hoping that submitting a screenshot > > of the alert will provide you some helpful information. If not, please > > let me know so I can stop wasting your time as well as mine. > > Generally, the more information the better. If you have an OS X > crash log or a screen shot of an internal error those can be good to > include. For the crash logs it can be good to include them as an > attachment since they can be fairly large.
Thanks for the clarification. It would be nice if there were a set of guidelines on the bug reporting site where we could refresh our memories on questions like these when we're submitting bug reports. > > If the debugger problem I encountered has indeed been fixed, I'm > > delighted. > > I suspect it was a problem trying to step while viewing stuff in the > new binary/contents pane of the debugger. This was an OS X only > problem that has been fixed. Please try the next build when it comes > out and if you still have problems let me know as soon as you can. I don't think it was related to viewing binary content. I've only done that once to confirm somebody else's report. My memory could be faulty on that though, and it COULD have occurred while or shortly after testing that report. I'll certainly be interested in testing the improvements in the next build. _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
