-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash Reports view: inadequate - more or less absent - instructions #73
Comments
Jeremy: thanks - I will investigate this, er, problem with the probem-reporting tool as soon as I have a chance. In the meantime, it would be helpful if you could find out how the tool (MintReport) is actually meant to work. Also, if what I see in MintReport is broken, then really the program itself should report the breakage. [EDIT: removed an extraneous word.] That is: seemingly there is a bug here in MintReport. |
I think MintReport is probably working fine - but because I'm not running the debug versions of virtually all programs, virtually all dumps don't have "useful" symbol tables. Have you considered whether |
Some months after opening this issue, I found my first crash report within Mint Report. So, Mint report is, sometimes, doing something (as @Jeremy7701 said). The point remains that_the program needs some instructions_. After all, if people cannot understand how Mint Report is meant to operate upon crash reports, then that will subvert the purpose for which the tool was created in the first place. |
I was asked to provide a stack trace via MintReport. So I open MintReport and (having clicked 'Crash Reports' - which, I note, lacks a tooltip) I see this:
Pondering suggests that were there extant crash reports then they would show in the top box. As for the bottom box: I have no idea. Nor do I see how I could know what to do, if I go merely by the window provides. EDIT: Nor does the 'Help' button actually provide any help - the button is misnamed.
The text was updated successfully, but these errors were encountered: